mylesborins

Director of Product for Codespaces here... AMA

This sounds SUPER interesting. Do you have an example of this? I wonder if this is something we could adopt in npm itself

Might make the most sense to kick off a thread in https://github.com/github/feedback/discussions/5962 so we can have a broader conversation

this is definitely on our radar! We didn't do any major work on artifacts / assets as part of this effort but there are a bunch of backlogged items, including individual hashes, that we would like to do in the future.

You can use a `.github/release.yml` to organize sections based on labels.

https://docs.github.com/en/repositories/releasing-projects-o...

I talked with one of the maintainers of conventional commits and we discussed writing an action to auto-label PRs based on conventional commits as a way to make a bridge between the two ways of working.

Here's an example workflow that automates publishing to npm and creating a release with generated notes on the push of a tag

https://github.com/MylesBorins/node-osc/blob/main/.github/wo...

The Release Notes are organized by PR and you can use configuration to sort into sections based on labels on those PRs. You can also ignore labels / particular users. So in theory everything you are outlining here is possible

https://docs.github.com/en/repositories/releasing-projects-o...

I guess it is a good thing we made automated release notes on GitHub use PRs instead of commits then ; )

Hey all, I'm the PM for this launch feel free to ask any questions

We are also collecting feedback in this discussion

https://github.com/github/feedback/discussions/5962

exactly

you two are both rad and this is the best interaction I've seen on the orange site in a while

exactly this. The base operating system comes with the system libraries necessary to support headless chrome out of the box.

(disclaimer: I work for Google Cloud)

You might want to take a look at our talk from Google I/O about the new runtime

https://www.youtube.com/watch?v=ogexnfng_hE&t=515s

The new runtime is 100% idiomatic without any special apis. We do offer certain native libraries pre compiled system libraries (to support headless chrome among other things) and certain ENV Variables for gcp API tokens.

You should be able to lift and shift a GAE Standard Node.js app to any other provider with minimal overhead.

I can't make direct promises regarding the runtime update cadence, but I can promise that I work closely with the people responsible for this and they care a lot about getting updates out in a timely fashion. The new runtime stack makes this easier to do than previous GAE Standard runtimes.

(Disclaimer: I work for GCP)

You can always set up a cron service

https://cloud.google.com/appengine/docs/standard/nodejs/sche...

https://github.com/GoogleCloudPlatform/nodejs-microservices-...

(I work for GCP)