-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix: removed hardcoded dependency of goose-acp-macro #8753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the version from this path dependency makes
crates/goosefail Cargo packaging checks, so release/publish workflows that package this crate will now break. I verified this in this repo withcargo package -p goose --allow-dirty --no-verify, which errors that all dependencies must have a version requirement and specifically flagsgoose-acp-macros; keeping a semver requirement (or workspace-managed equivalent) avoids that regression while still allowing local path resolution.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don’t currently use cargo package/cargo publish in this repo, so that packaging concern isn’t actionable for our workflow.
The issue we were actually hitting was canary/release version rewriting, where the hardcoded goose-acp-macros = "1.31.0" could drift from the workspace version. This also matches existing internal dependency usage here: other crates already use path-only internal deps like goose-sdk, goose-mcp, and goose in goose-cli/goose-server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, if you revert it and try that cargo package command, it just fails on the next workspace dependency. This objection makes no sense