Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Cut first release tag (vX.Y.Z) once PR #85 merges to main #87

New Issue
Closed
opened 2026-08-09 10:16:27 +00:00 by Claude · 1 comment
Claude commented 2026-08-09 10:16:27 +00:00
Collaborator
Copy Link

PR #85 adds .pre-commit-hooks.yaml, exposing kyberforge-vale-audit-skill, kyberforge-vale-audit-agent, and kyberforge-skill-size-check for external repos to consume via repo: <this-repo-url>, rev: <tag> in their own .pre-commit-config.yaml (see ADR-0014).

This repo has no tags yet. External consumers need a rev: to pin. The tag was deliberately not cut on the feature branch — tagging pre-merge risks pinning a commit that doesn't survive a squash-merge onto main.

Action: once PR #85 merges, cut the first tag (e.g. v1.0.0) on main and push it.

Going forward: scripts/check-release-needed.sh (wired at pre-push, main-only) hard-fails if files exposed via .pre-commit-hooks.yaml change without a covering tag, so future releases shouldn't need a manually-tracked reminder like this one — this is the last one-off.

PR #85 adds `.pre-commit-hooks.yaml`, exposing `kyberforge-vale-audit-skill`, `kyberforge-vale-audit-agent`, and `kyberforge-skill-size-check` for external repos to consume via `repo: <this-repo-url>, rev: <tag>` in their own `.pre-commit-config.yaml` (see ADR-0014). This repo has no tags yet. External consumers need a `rev:` to pin. The tag was deliberately **not** cut on the feature branch — tagging pre-merge risks pinning a commit that doesn't survive a squash-merge onto `main`. **Action:** once PR #85 merges, cut the first tag (e.g. `v1.0.0`) on `main` and push it. **Going forward:** `scripts/check-release-needed.sh` (wired at `pre-push`, main-only) hard-fails if files exposed via `.pre-commit-hooks.yaml` change without a covering tag, so future releases shouldn't need a manually-tracked reminder like this one — this is the last one-off.
Claude commented 2026-08-10 16:48:52 +00:00
Author
Collaborator
Copy Link

PR #85 merged to main at 8f523da. Tagged and released v1.0.0 from that commit: https://git.dev.rkdr.net/Defame1297/holocron/releases/tag/v1.0.0

External consumers can now pin .pre-commit-hooks.yaml's exposed hooks (kyberforge-vale-audit-skill, kyberforge-vale-audit-agent, kyberforge-skill-size-check) via rev: v1.0.0.

PR #85 merged to `main` at `8f523da`. Tagged and released `v1.0.0` from that commit: https://git.dev.rkdr.net/Defame1297/holocron/releases/tag/v1.0.0 External consumers can now pin `.pre-commit-hooks.yaml`'s exposed hooks (`kyberforge-vale-audit-skill`, `kyberforge-vale-audit-agent`, `kyberforge-skill-size-check`) via `rev: v1.0.0`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#87
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?