Skip to content

chore: sync dev with main#45

Open
vig-os-release-app[bot] wants to merge 1 commit intodevfrom
chore/sync-main-to-dev-15-1
Open

chore: sync dev with main#45
vig-os-release-app[bot] wants to merge 1 commit intodevfrom
chore/sync-main-to-dev-15-1

Conversation

@vig-os-release-app
Copy link
Copy Markdown
Contributor

Syncs dev with main (sync-main-to-dev workflow).

Drives version bumps, tagging, and publish triggers from conventional
commits for both Python (py-materials → PyPI) and Rust (rs-materials →
crates.io, gated) packages.

Pipeline on push to main:
1. release-please scans commits since the last tag and opens a
   per-package Release PR bumping versions + appending CHANGELOG
   entries.
2. Merging the Release PR pushes a tag (vX.Y.Z or
   rs-materials/vX.Y.Z), which triggers the existing publish
   workflows.
3. release-please creates the GitHub Release with auto-generated
   notes — the duplicate `github-release` jobs in release.yml and
   release-rs-materials.yml are removed.

Also:
- PR Hygiene job enforces the contributor PR template checklist via
  mheap/require-checklist-action. Template restructured into
  "required" (must be checked) and "if applicable" (delete sections
  that don't apply) groups. Bot PRs from release-please are exempt
  (they carry their own release-reviewer checklist for humans).
- rs-materials crates.io publishing is gated behind
  vars.CRATES_IO_PUBLISH_ENABLED until the token is configured and
  downstream consumer coordination completes (issue #43).
- Uses the existing RELEASE_APP GitHub App so the tag release-please
  pushes triggers downstream workflows (GITHUB_TOKEN pushes are inert
  under recursion protection).

Refs: #43
@vig-os-release-app vig-os-release-app Bot enabled auto-merge April 18, 2026 16:25
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