Skip to content

docs: add Veilid upgrade skill#33

Merged
tripledoublev merged 5 commits into
mainfrom
docs/veilid-upgrade-skill
Jun 29, 2026
Merged

docs: add Veilid upgrade skill#33
tripledoublev merged 5 commits into
mainfrom
docs/veilid-upgrade-skill

Conversation

@tripledoublev

Copy link
Copy Markdown
Contributor

Summary

  • add a repo-local Claude skill for the Veilid cross-repo upgrade cascade
  • add a dependency map reference covering repo order, pins, verification, and fork-origin migration boundaries
  • add CLAUDE.md and AGENTS.md pointers so Claude Code and Codex can discover the runbook

Verification

  • python3 /home/v/.codex/skills/.system/skill-creator/scripts/quick_validate.py .claude/skills/veilid-upgrade
  • rg -n "line [0-9]|0.5.4|v0.5.4|0.5.5|v0.5.5|0.3.11|0.2.8" .claude/skills/veilid-upgrade CLAUDE.md AGENTS.md

tripledoublev and others added 5 commits June 29, 2026 17:41
- nextest filter expressions now use -E (a bare quoted string is a
  substring match and silently runs 0 tests)
- save-dweb-backend runs the full nextest suite (its CI does); drop the
  save-rust-only smoke names that do not exist in that repo
- stale-tag verification greps a concrete previous version instead of the
  no-op literal 0\.5\.x
- tag step checks out the default branch first so the tag lands on the
  merge commit, not the feature branch tip

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ease tags

- Tag step no longer assumes 'origin' is the release repo. veilid-iroh-blobs
  may have origin=RangerMauve and a separate openarchive remote, so confirm
  with 'git remote -v' and push the tag to the merged-into remote.
- Fork-origin migration checklist now distinguishes 'do not change Veilid
  version tags' from 'you may need to cut new wrapper-crate release tags';
  bump the package version and tag a new version rather than moving a tag.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A pushed git tag does not appear on the Releases page; these repos keep a
Release per tag. Add a 'gh release create' step after the tag push, and
note that Releases should be created only for tags on the merged default
branch, after all PRs for the upgrade have merged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tripledoublev tripledoublev merged commit e3b4dee into main Jun 29, 2026
1 check passed
@tripledoublev tripledoublev deleted the docs/veilid-upgrade-skill branch June 29, 2026 23:10
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