Skip to content

Comments

Promote job version handling#230

Closed
cursor[bot] wants to merge 2 commits intomainfrom
cursor/promote-job-version-handling-6575
Closed

Promote job version handling#230
cursor[bot] wants to merge 2 commits intomainfrom
cursor/promote-job-version-handling-6575

Conversation

@cursor
Copy link

@cursor cursor bot commented Feb 20, 2026

Bare minimum self-checks

What do you think of a person who only does the bare minimum?

  • I've updated this PR with the latest code from main
  • I've done a cursory QA pass of my code locally
  • I've ensured all automated status check and tests pass
  • I've connected this PR to an issue

Pieces of flare

  • I've written a unit or functional test for my code
  • I've updated relevant documentation it my code changes it
  • I've updated this repo's README if my code changes it
  • I've updated this repo's CHANGELOG with my change unless its a trivial change (like updating a typo in the docs)

Finally

If you have any issues or need help please join the #contributors channel in the Lando slack and someone will gladly help you out!

You can also check out the coder guide.


Fixes a bug where the promote job in release.yml would read an incorrect version from package.json for npm dist-tag add. The promote job now correctly derives the version directly from github.event.release.tag_name (stripping the 'v' prefix), ensuring latest points to the intended release version.


AaronFeledy and others added 2 commits February 19, 2026 19:55
Adds an 'edited' trigger to the release workflow with a lightweight 'promote' job that runs npm dist-tag to move 'latest' to the current version. Only fires when a prerelease is changed to a full release (not drafts). The existing publish pipeline remains gated to 'published' events only.
The promote job now derives VERSION from github.event.release.tag_name
instead of reading package.json. This ensures it points the 'latest'
npm dist-tag to the correct prerelease version that was actually
published, rather than the stale version in the tagged commit's
package.json.
@cursor
Copy link
Author

cursor bot commented Feb 20, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

Base automatically changed from feature/promote-edge-on-edit to main February 20, 2026 03:16
@cursor cursor bot closed this Feb 20, 2026
@cursor
Copy link
Author

cursor bot commented Feb 20, 2026

Automatically closed this PR because it was created by Bugbot autofix for #229, and that PR was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants