Skip to content

chore(deps): bump workshop-rs from 0.3.7 to 1.0.0 - #121

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/workshop-rs-1.0.0
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/workshop-rs-1.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor

Bumps workshop-rs from 0.3.7 to 1.0.0.

Release notes

Sourced from workshop-rs's releases.

v1.0.0

What's Changed

Full Changelog: wrightkit/workshop-rs@v0.11.0...v1.0.0

v0.11.0

What's Changed

Full Changelog: wrightkit/workshop-rs@v0.10.0...v0.11.0

v0.10.0

What's Changed

Full Changelog: wrightkit/workshop-rs@v0.9.1...v0.10.0

v0.9.1

What's Changed

Full Changelog: wrightkit/workshop-rs@v0.9.0...v0.9.1

v0.9.0

What's Changed

Full Changelog: wrightkit/workshop-rs@v0.8.0...v0.9.0

v0.8.0

What's Changed

... (truncated)

Changelog

Sourced from workshop-rs's changelog.

Release automation

workshop-rs keeps crate publication and binary distribution deliberately simple and separate.

  • release-plz owns Release PR maintenance, crates.io publication, and the single canonical vX.Y.Z tag.
  • A repository-owned tag workflow builds workshop-rs-cli for the supported targets, packages the binaries, generates checksums and catalog-identity.json, then creates the GitHub Release once the complete artifact set is ready.

The repository follows the WrightKit release engineering standard. This document records only the repo-local contract.

Release identity

The workspace crates share one version group:

  • workshop-rs
  • workshop-rs-cli

workshop-rs owns the single public tag:

vX.Y.Z

release-plz does not create the GitHub Release. The tag is the only normal trigger for binary distribution.

Repository configuration

GitHub automation token

release-plz uses GH_TOKEN for Release PR and tag operations.

A dedicated token is intentional here because the tag pushed by release automation must trigger the separate tag-based Release workflow. Do not replace it with the workflow-provided GITHUB_TOKEN without re-validating event propagation.

crates.io token

CARGO_REGISTRY_TOKEN is stored in the protected release environment and must be able to publish both workspace crates.

Moving to crates.io Trusted Publishing / OIDC is a separate credential migration. Do not combine that change with unrelated release-topology work unless both boundaries are independently validated.

Concurrency

The release-plz publication job uses a stable concurrency group with cancel-in-progress: false. A newer push to main must not cancel an in-progress registry publication.

The tag workflow likewise allows only one active release run per tag and does not cancel an in-progress release.

Normal release flow

Normal pushes to main run two release-plz jobs:

  1. release-plz release publishes any releasable workspace versions to crates.io and creates the canonical vX.Y.Z tag.
  2. release-plz release-pr creates or refreshes the next Release PR.

... (truncated)

Commits
  • 606c5e2 feat(api): establish the stable 1.0.0 release (#322)
  • afac13f docs: define the 1.x compatibility policy for catalog, behavior, and output c...
  • c02816d chore: release v0.11.0 (#320)
  • 5110885 refactor!: remove duplicate public paths before 1.0 (#319)
  • 3d6e6e8 chore: release v0.10.0 (#318)
  • 35f1528 refactor(api)!: mark growing public types #[non_exhaustive] (#317)
  • 359df0c refactor!: remove catalog-generated typed constructors from the public API (#...
  • 311ff50 chore: release v0.9.1 (#309)
  • 7e25fd5 test(element-count): cover player-variable target costs (#310)
  • 0c64104 fix(analysis): count elements the way the client-checked OverPy counter does ...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [workshop-rs](https://github.com/wrightkit/workshop-rs) from 0.3.7 to 1.0.0.
- [Release notes](https://github.com/wrightkit/workshop-rs/releases)
- [Changelog](https://github.com/wrightkit/workshop-rs/blob/main/docs/release.md)
- [Commits](wrightkit/workshop-rs@v0.3.7...v1.0.0)

---
updated-dependencies:
- dependency-name: workshop-rs
  dependency-version: 1.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 1, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #133.

@dependabot dependabot Bot closed this Nov 1, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/workshop-rs-1.0.0 branch November 1, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants