chore: bump VibeTags to 1.2.0 - #68
Merged
Merged
Conversation
1.2.0 lets a library publish package-level guardrails that consuming projects inherit. Both halves are file-presence opt-ins (.vibetags-manifest to publish, .vibetags-transitive to consume) and neither file exists here, so this bump changes no generated file: the diff is the version declaration. It also fixes a bug that mattered for every Gradle consumer — transitive discovery skipped itself under Gradle, because Gradle wraps the ProcessingEnvironment and Trees.instance rejects anything that is not javac's own. Verified by building this branch against the artifacts as published on Maven Central, with the locally installed 1.2.0 purged first so nothing resolved from ~/.m2. Generated guardrail files are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H3k21o8evnUvw58WDXWx4u
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps VibeTags to 1.2.0 (release notes).
What 1.2.0 adds
Package-level guardrails can now travel from a library into the projects that depend on it. A
library annotates a
package-info.javaand drops a.vibetags-manifest; a consumer drops a.vibetags-transitiveand gets those rules rendered into its own AI config under## Inherited Guardrails (dependencies).Both halves are file-presence opt-ins that do not exist in this repo, so this bump changes no
generated file. It is available if we want it later.
Also fixed in 1.2.0, and relevant to any Gradle build: transitive discovery was skipping itself
under Gradle entirely, because Gradle wraps the
ProcessingEnvironmentandTrees.instancerejectsanything that is not javac's own. Found by wiring the feature up across these repos before the
release, not after.
Verification
The build ran on this branch against the artifacts as published on Maven Central — the local 1.2.0
was purged from
~/.m2first, so nothing resolved from a local install. Generated guardrail filesare unchanged; the diff is the version declaration only.