Repository navigation
chore(release): 0.45.0 + stable branch for the plugin directory (#768) - #792
Open
CSalcedoDataBI wants to merge 2 commits into
Open
CSalcedoDataBI wants to merge 2 commits into
CSalcedoDataBI wants to merge 2 commits into
Conversation
… release (#768) The directory scans every commit on the branch it tracks and each one replaces the version in review, so tracking main would restart the review on every merge. The Release workflow now fast-forwards stable to each released commit, beside the existing release channel, with the same no-force rule. CONTRIBUTING documents the cadence: batch work, test locally before a release, no release while a version is in review except security fixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Sin hallazgos: bump a 0.45.0 consistente en |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #768.
What merging this does (the Release workflow fires on the \plugin.json\ version change):
elease, the branch installs fetch.
Why: the directory scans every commit on the branch it tracks, and each one replaces the version in review. Pointing it at \stable\ instead of \main\ means only releases reach review.
v0.45.0 carries everything since v0.44.0, including the directory fixes (#789, #790, #791). The CHANGELOG block was curated by hand: \New-Release.ps1\ only folded 6 board issues and stripped the file's BOM, and both are fixed here.
Checks: \New-Release -Check\ OK, \Update-Docs -Check\ OK, \claude plugin validate --strict\ OK on the plugin and the marketplace, directory checker 0 blocking.
After merge (owner): in the portal, Ajustes → Origen → Branch \stable\ → Guardar. This restarts the review queue once.
🤖 Generated with Claude Code