Skip to content

fix(ci): fix release-please config to match working norm setup#84

Open
MariusVolkhart wants to merge 1 commit into
mainfrom
fix/release-please-config
Open

fix(ci): fix release-please config to match working norm setup#84
MariusVolkhart wants to merge 1 commit into
mainfrom
fix/release-please-config

Conversation

@MariusVolkhart

Copy link
Copy Markdown
Member

Summary

  • Move extra-files from root level into packages["."] block — release-please-action v5 ignores root-level extra-files
  • Remove search/replace regex fields — Generic updater v17 uses x-release-please-version block annotations instead
  • Add # x-release-please-start-version / # x-release-please-end annotations to gradle.properties
  • Delete post-release.yml — GitHub blocks release: published event when release is created by GITHUB_TOKEN, so the SNAPSHOT bump never fired
  • Move SNAPSHOT bump logic into release-please.yml, guarded by release_created output
  • Use release-please's major/minor/patch outputs instead of parsing gradle.properties
  • Remove unused changelog-sections and generate-release-notes config
  • Add release process documentation to CONTRIBUTING.md

All fixes were discovered and validated in the norm project (commits 335c87b, a321779, 041a575, fe8e183).

🤖 Generated with Claude Code

release-please-action v5 ignores root-level extra-files — move into
packages["."] block. Generic updater v17 ignores search/replace fields
and uses x-release-please-version annotations instead — add block
annotations to gradle.properties and drop the regex fields.

Separate post-release.yml used `on: release: published`, but GitHub
blocks that event when the release is created by GITHUB_TOKEN. Move
the SNAPSHOT bump into release-please.yml, guarded by release_created
output, using release-please's own major/minor/patch outputs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@MariusVolkhart MariusVolkhart force-pushed the fix/release-please-config branch from 4fe7294 to f75ed74 Compare June 3, 2026 15:23
@snyk-io

snyk-io Bot commented Jun 3, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

with:
token: ${{ secrets.GITHUB_TOKEN }}

- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
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