build(deps): Bump praxis-proxy/conventions/.github/actions/setup-rust from dc77dbd3a55ce96e8e31a3c8d36cea4952617dd3 to bcfaea95ff4e6746587d54f6b6d6a62cfc5aa0e4

[dependabot]

Bumps praxis-proxy/conventions/.github/actions/setup-rust from dc77dbd3a55ce96e8e31a3c8d36cea4952617dd3 to bcfaea95ff4e6746587d54f6b6d6a62cfc5aa0e4.

Changelog

Sourced from praxis-proxy/conventions/.github/actions/setup-rust's changelog.

Release Process

Versioning

Releases use Semantic Versioning. The workspace version is the single source of truth, defined in workspace.package.version in the root Cargo.toml. All workspace crates inherit this version.

Pre-release Checklist

Before tagging a release:

• Lints are clean (make lint)
• All tests pass locally (make test)
• Dependency audit passes (make audit)
• SemVer compliance verified (make semver)
• Version in root Cargo.toml is bumped (both workspace.package.version and any workspace.dependencies inter-crate versions)
• Cargo.lock is regenerated with the new version
• make publish-dry-run succeeds (add --allow-dirty when running against uncommitted changes)
• SECURITY.md lists the new minor version
• GitHub Release changelog is drafted (see below)

Tagging a Release

Tags follow the format v<MAJOR>.<MINOR>.<PATCH> (e.g. v0.1.0) and must match workspace.package.version; the release workflow rejects mismatched tags. Push the tag to the repository:

git tag v0.1.0
git push origin v0.1.0

Pushing the tag runs the release pipeline (.github/workflows/release.yaml):

1. Validate the tag against the workspace version
2. Run the full test suite
3. Verify every release crate packages cleanly (publish dry run)
4. Build and publish the container image to GHCR
5. Create the GitHub release with generated notes

... (truncated)

Commits

• bcfaea9 ci(release): add draft pre-release, publish on maintainer publish
• 9eea211 ci: add timeout-minutes to all jobs
• c6f5266 ci: track base images with dependabot
• ef3e870 ci: add issue-triage workflow to mark new issues for triage
• 9e4a1ee docs: fix broken links
• 02a02df docs(maintainers): fix table formatting to satisfy lint
• 1b5d834 chore(deps): cargo update
• 766538c docs: redirect proposals to centralized enhancements repo
• 9d9d782 docs: update governance
• 92b0445 Merge pull request #1 from rikatz/improve-ci-conventions
• Additional commits viewable in compare view

[shaneutt]

@dependabot recreate

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.