Skip to content

build: publish the codegen crate as worktable_macros - #173

Merged
pathscale merged 1 commit into
masterfrom
build/rename-codegen-to-worktable-macros
Jul 27, 2026
Merged

build: publish the codegen crate as worktable_macros#173
pathscale merged 1 commit into
masterfrom
build/rename-codegen-to-worktable-macros

Conversation

@pathscale

Copy link
Copy Markdown
Owner

Unblocks the 0.9.0 release. worktable_codegen on crates.io has a single external owner (Handy-caT), so this project cannot publish worktable_codegen 0.9.0 — and worktable pins =0.9.0, so the release was stuck.

Rename the package to worktable_macros (the conventional name for a proc-macro companion crate — tokio-macros, pyo3-macros) and publish under that name, which is unclaimed.

Only the package name changes:

  • the lib target keeps the worktable_codegen name, and
  • the root manifest uses a renamed dependency (worktable_codegen = { package = "worktable_macros", ... }),

so every use worktable_codegen::… and the worktable_codegen/s3-support feature reference stay untouched. Zero source changes.

Verified: full suite green (316 passed), cargo fmt / clippy --all-targets clean, cargo publish --dry-run -p worktable_macros packages and compiles.

Release sequence after merge: publish worktable_macros 0.9.0 → publish worktable 0.9.0 → tag v0.9.0.

🤖 Generated with Claude Code

crates.io ownership of worktable_codegen is not available to this
project (the crate has a single external owner), which blocks releasing
0.9.0: worktable pins the codegen crate to =0.9.0, and that version can
never be published under the old name. Rename the package to
worktable_macros -- the conventional name for a proc-macro companion
crate -- and publish under it instead.

Only the package name changes. The lib target keeps the
worktable_codegen name and the root manifest uses a renamed dependency,
so every `use worktable_codegen::...` and the
`worktable_codegen/s3-support` feature reference stay untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pathscale
pathscale merged commit 9787b2f into master Jul 27, 2026
2 checks passed
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