chore(main): release rs-materials 1.0.0#55
Closed
vig-os-release-app[bot] wants to merge 1 commit intomainfrom
Closed
chore(main): release rs-materials 1.0.0#55vig-os-release-app[bot] wants to merge 1 commit intomainfrom
vig-os-release-app[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
gerchowl
added a commit
that referenced
this pull request
Apr 18, 2026
Three coordinated tightenings for the release pipeline post-3.0: 1. **Disable rs-materials in release-please** until crates.io publish enables (#43). While the publish path is gated behind `CRATES_IO_PUBLISH_ENABLED`, release-please tracking rs-materials produces only false-bump Release PRs (#50, #55) — every push to main re-opens them. Removing the package entry stops the inflation. Re-add when #43 lands, with `bump-minor-pre-major: true` to keep pre-1.0 versioning sane. 2. **Wire commitizen as commit-msg hook.** The .githooks/commit-msg script invoked `pre-commit run --hook-stage commit-msg` but no commit-msg-stage hooks were configured — the standard in docs/COMMIT_MESSAGE_STANDARD.md was documentation-only with zero enforcement. Add commitizen pinned to v4.13.9. Conventional-commit format is now validated at commit time. 3. **Document the scope taxonomy.** Multi-package monorepo benefits from per-package scopes: (py) — py-materials Python package (rs) — rs-materials Rust crate (data) — TOML data shared between py + rs (vis) — vis subsystem (Python, mat-vis-client integration) (deps) — dependency bumps (ci) — CI / release pipeline (docs) — documentation Documented in COMMIT_MESSAGE_STANDARD.md with rationale linking to the cross-cutting-bump issues (#50, #55). Scope membership is social convention; format is enforced by commitizen. Refs: #43
7 tasks
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.
🤖 Automated release. Merging this PR creates a tag, which fires the publish workflow (PyPI for
py-materials, crates.io forrs-materials).Release Reviewer Checklist
Check before merging. PR Hygiene CI is intentionally skipped on release-please PRs — these boxes are for the human merging the release.
feat!:)1.0.0 (2026-04-18)
⚠ BREAKING CHANGES
properties.pbrremoved,.viscanonical, mat-vis-client 0.4.x (#52)Added
properties.pbrremoved,.viscanonical, mat-vis-client 0.4.x (#52) (49b5dff)Fixed
This PR was generated with Release Please. See documentation.