Skip to content

chore: bump copypatch 0.2.0-rc.5 and weavy 0.2.3-rc.0 - #10

Merged
fasterthanlime merged 1 commit into
mainfrom
deps/bump-for-publish
Aug 19, 2026
Merged

fasterthanlime merged 1 commit into
mainfrom
deps/bump-for-publish

Conversation

@fasterthanlime

Copy link
Copy Markdown
Contributor

crates.io weavy 0.2.2 / copypatch 0.2.0-rc.4 are still the old facet-rs/facet crates. release-pr dies comparing them to weavy history: a542bb3 has edition.workspace and no workspace root.

This bumps to unpublished versions so release-plz skips that compare and publishes on merge:

  • copypatch 0.2.0-rc.4 → 0.2.0-rc.5
  • weavy 0.2.2 → 0.2.3-rc.0

weavy depends on copypatch ^0.2.0-rc.5, so release-plz must publish copypatch first (it will). After that, phon can pin crates.io weavy.

Local: cargo package -p copypatch verifies. cargo package -p weavy correctly fails until copypatch rc.5 is on crates.io. 234 tests pass.

crates.io still has the old facet-rs weavy 0.2.2 / copypatch 0.2.0-rc.4.
release-plz release-pr dies comparing those against weavy history
(a542bb3 has no workspace root, edition.workspace fails).

Unpublished versions skip that compare. Merging this lets release-plz
publish the bearcove crates. weavy depends on copypatch ^0.2.0-rc.5, so
copypatch publishes first.
@fasterthanlime
fasterthanlime merged commit f14bb3f into main Aug 19, 2026
6 checks passed
@fasterthanlime
fasterthanlime deleted the deps/bump-for-publish branch August 19, 2026 21:26
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.

2 participants