chore: release v4.202607.0#164
Merged
Merged
Conversation
Version bump + changelog for the 4.202607.0 release. Done via PR because the release workflow's workflow_dispatch path pushes the bump commit directly to main, which the branch-protection rulesets reject (GH013). After this merges, pushing the v4.202607.0 tag triggers the workflow's tag path (resolve-version -> publish), which does not push to main and publishes cleanly. Includes: self-contained OS-portable VS Code .vsix (#159), CAP 10 + cds-10 drivers (#160), TypeScript 7 for extension/mcp-server + consolidated deps (#160, #162), Group B majors (#162), i18n key fixes (#163).
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.
Release v4.202607.0
Version bump + changelog for the
4.202607.0release.Why a PR (not the dispatch button)
The
Release hana-cliworkflow'sworkflow_dispatchpath runs apreparejob that pushes the version-bump commit directly tomain— which the branch-protection rulesets reject (GH013: Repository rule violations). So the bump is done here as a PR instead.After this merges, pushing the
v4.202607.0tag triggers the workflow's tag path (resolve-version → publish), which does not push to main and publishes to npm + creates the GitHub release + MCP registry cleanly.What's in this release
.vsixshipped via npm —hana-cli vscode install, bundled web UI,node:sqlite, no native binaries (fix(vscode): ship self-contained, OS-portable .vsix via npm #159)@sap/cds10) + cds-10-native drivers, removed@sap/cds-hana(chore(deps): consolidated dependency update + CAP 10 upgrade #160)vscode+error.cfNotLoggedIni18n keys across all 9 locales (fix(i18n): add missing vscode + error.cfNotLoggedIn keys to all locales #163)Files
package.json,npm-shrinkwrap.json,server.json,mcp-server/package.json,mcp-server/npm-shrinkwrap.json→4.202607.0(mcp-server →1.202607.0);CHANGELOG.json/CHANGELOG.mdupdated.Follow-up note
Consider updating the release workflow so
workflow_dispatchopens a release PR (or adds a bypass actor) instead of pushing tomain— the current dispatch path can't succeed under the active rulesets.