Skip to content
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

Merged
merged 5 commits into from
Mar 5, 2024
Merged

[ci] set --tag on release #10323

merged 5 commits into from
Mar 5, 2024

Conversation

natemoo-re
Copy link
Member

@natemoo-re natemoo-re commented Mar 4, 2024

Changes

  • We currently don't have a process for backporting fixes to previous release branches
  • We do currently release from the main, next, and 1-legacy / 2-legacy / 3-legacy branches
  • When we recently cut a release from 3-legacy, it was published to latest on NPM! Thankfully we released from main shortly thereafter, but it could be annoying to debug if we forget to do that in the future.
  • This PR automates the process so we don't have to think about it again. The code comments hopefully provide enough context.
  • Closes PLT-1750

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.

Copy link

changeset-bot bot commented Mar 4, 2024

⚠️ No Changeset found

Latest commit: 3a14588

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added the 🚨 action Modifies GitHub Actions label Mar 4, 2024
Copy link
Member

@ematipico ematipico left a 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

@natemoo-re natemoo-re merged commit 50215ae into main Mar 5, 2024
13 checks passed
@natemoo-re natemoo-re deleted the chore/action-publish-tag branch March 5, 2024 22:43
FredKSchott added a commit that referenced this pull request Mar 6, 2024
@FredKSchott FredKSchott mentioned this pull request Mar 6, 2024
FredKSchott added a commit that referenced this pull request Mar 6, 2024
* Revert "[ci] release (#10332)"

This reverts commit dd3935b.

* Revert "[ci] set `--tag` on release (#10323)"

This reverts commit 50215ae.
peng added a commit to peng/astro that referenced this pull request Mar 6, 2024
* 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 action Modifies GitHub Actions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants