David Sherret

@andrewvijay @JLarky I saw that one. I don't see it doing this pinning, but for generating the YAML I had different goals. I'm not so concerned about type safety within different actions and wanted a way to do propagate conditions backwards to other steps (more detail in david.deno.dev/posts/gagen/)

@DavidSherret @JLarky's gha-ts does the same! github.com/JLarky/gha-ts

I've found maintaining GitHub Actions workflow files is much easier when it's generated from Typescript. The latest realization is that the output yaml file can act like a lockfile. So I maintain `actions/checkout@v6`, but the generated output gets locked to a hash.

@_ndianabasi It gets the hash from the git tag then pins to that.

@DavidSherret Is the hash generated from the commit hash for the release? Or it's generated from logic within your library? The former is preferable for supply-chain attack mitigation.

For how we used this in Deno's repo, see this blog post david.deno.dev/posts/gagen/

I've published a library here that also has tooling around this github.com/dsherret/gagen

@makka_me @nodejs Bun didn’t ever respond to any of my security reports. They just silently fixed them and didn’t publish anything. Their repo has zero security advisories.

@nodejs Will there be any reason to use Node over Bun soon? Bun is faster, and they have committed to be 100% Node compatible (excluding bugs)

⚠️ Update: The Node.js project's security bug bounty program is being paused. Reporting remains unchanged, and so does our commitment to security. More details here: nodejs.org/en/blog/announ…

@bentlegen @lucyhargreaves4 Not sure about other numbers or his overall performance, but that number has been going up since he's been CEO—now at 73.26% on time in 2025. Also, Canadian airlines have to deal with snow more than US airlines. Someone I know who works at the airline really likes what he's done.

@lucyhargreaves4 That's a reasonable argument, but ... I have never seen anybody on this platform praise Air Canada's leadership/competence, ever – usually the opposite

this is the wrong outcome it’s insane we continue to prioritize things like bilingualism over competence

I'm also working on support for plugins distributed on npm and support for using node resolution to resolve plugins. This should help users who have IT/compliance constraints.

For the official process plugins, I was unfortunately using absolute URLs in the plugin manifests, so you'll need to run `dprint config update` to get better reliability for those.

Due to terrible GitHub availability, dprint formatting plugins on plugins.dprint.dev are now served directly instead of redirecting to GH assets. Additionally, the plugins are now cached indefinitely by the server, which eliminates the risk of a repo disappearing.

Also released new versions of jsonc-morph (github.com/dsherret/jsonc…) for JavaScript, dprint-plugin-json, and dprint-plugin-jupyter, so those projects include these performance improvements.

Released jsonc-parser 0.32, which allows deserializing via serde to a concrete type. It's also much faster.

I’m no longer at Deno. Grateful to have worked alongside such a strong team and contribute to the CLI. Excited for what’s next, I’m open to new opportunities.

Last Monday was my last day at Deno. It was a privilege to work with such talented colleagues. The standard library has been my passion for years. I've reviewed all PRs since 2023 and learned a lot from them. Proud to see it often mentioned as one of the best parts of Deno.

@kdy1dev Thanks!

@DavidSherret Wishing you the best, David

Yesterday was my last day at Deno. I'm going to transition from two days a week to full time on a business I cofounded in the auto glass industry. My plan is to increase my contributions to my open source projects and keep contributing features/fixes to Deno that I need or want.

Satya is an excellent developer and pleasant person to be around. We joined Deno around the same time. Now’s your opportunity to hire him.

@eddiejaoude Thanks!

@DavidSherret all the best with your next chapter David

@_dr5w Thanks! Yes and most of the CLI team is still there working on it. I'm looking forward to some of the upcoming changes (though now they can do stuff without me arguing against it, which is either a good or bad thing 😛)

@DavidSherret Enjoyed seeing you around in issues. Do you think Deno as a product and company is in a good spot for the near future?

There's so many cool things under Deno's hood that we haven't talked about so I'll also take some time to blog or post about them soon.

It's been an incredible privilege to have been paid to spend these last five years working with extremely talented colleagues designing, implementing, and refactoring a large portion of Deno.