-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] set --tag
on release
#10323
[ci] set --tag
on release
#10323
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
This reverts commit 50215ae.
* main: [ci] release (withastro#10337) Revert bad release (withastro#10336) [ci] release (withastro#10332) add missing changeset (withastro#10335) [ci] set `--tag` on release (withastro#10323) [ci] format add back data loss confirmation handling (withastro#10330) [ci] format fix(rendering): allow render instructions to propagate while rendering slots (withastro#10316) [ci] format fix: fixed an error in the vue component editor (withastro#10293) chore(vercel): update @vercel/nft (withastro#10305) Update turbo test dependsOn (withastro#10329) Add minimal @astrojs/db readme (withastro#10331)
Changes
main
,next
, and1-legacy
/2-legacy
/3-legacy
branches3-legacy
, it was published tolatest
on NPM! Thankfully we released frommain
shortly thereafter, but it could be annoying to debug if we forget to do that in the future.Testing
Contrary to my typical YOLO approach, I actually minimized this workflow and tested it in a private repo. Everything works as expected!
Docs
Currently, our actions are super undocumented. Currently attempting to kick off an effort to get more of these decisions documented, but until then, code comments should suffice.