Skip to content

chore: keep install-snippet versions in sync via release-please - #87

Merged
emaarco merged 1 commit into
mainfrom
chore/sync-version-references
Aug 19, 2026
Merged

chore: keep install-snippet versions in sync via release-please#87
emaarco merged 1 commit into
mainfrom
chore/sync-version-references

Conversation

@emaarco

@emaarco emaarco commented Aug 19, 2026

Copy link
Copy Markdown
Member

What & why

Version numbers were scattered and contradictory: the authoritative version (gradle.properties = 5.2.0, matching tag v5.2.0) was bumped by release-please, but every hand-maintained install snippet had drifted — the top-level README and all docs said 6.0.0, the module READMEs said 3.0.0.

Root cause: release-please only listed gradle.properties in extra-files, so nothing else stayed in sync.

Changes

  • Reconcile every install snippet to the published 5.2.0 (README.md, both module READMEs, docs/getting-started/*, docs/validate/*, docs/surface/json.md).
  • Wrap each snippet in invisible <!-- x-release-please-start-version --> / <!-- x-release-please-end --> HTML-comment markers (outside the code fence, so nothing renders in the copy-paste block).
  • Register those files as generic extra-files in release-please-config.json, so the standing Release PR now bumps them atomically with gradle.properties.
  • Update the release skill to reflect that the Release PR now also bumps the README/docs snippets.

Version-specific migration guides and ADRs (e.g. docs/changelog/v6.md, prose like "Since 6.0.0 the format …") are intentionally left untouched.

Verification

  • release-please-config.json remains valid JSON.
  • No 6.0.0/3.0.0 left in install snippets (only the intentional historical prose reference).
  • Start/end markers balanced (13/13).
  • End-to-end: the next Release PR will show all registered files updated with the new version (previewable via the release-please.yml workflow_dispatch dry run).

Register the READMEs and docs install snippets as release-please extra-files
and wrap each version in invisible HTML-comment markers, so the standing
Release PR bumps them atomically with gradle.properties. Reconcile all
snippets to the published 5.2.0 (they had drifted to 6.0.0 / 3.0.0).
@emaarco
emaarco enabled auto-merge (squash) August 19, 2026 13:36
@emaarco emaarco self-assigned this Aug 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Test Coverage

Module Line Coverage
bpmn-to-code-core 97.6% (2244/2300 lines)
bpmn-to-code-gradle 25.7% (29/113 lines)
bpmn-to-code-maven 62.2% (28/45 lines)
bpmn-to-code-web 95.6% (196/205 lines)
bpmn-to-code-testing 97.2% (171/176 lines)
bpmn-to-code-runtime 100.0% (80/80 lines)

@emaarco
emaarco merged commit dc0d01f into main Aug 19, 2026
5 checks passed
@emaarco
emaarco deleted the chore/sync-version-references branch August 19, 2026 13:37
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.

1 participant