vanity
Skill1.1k starsChanged 7 months agoApache-2.0View on GitHub
Registers node major version vanity URL in the sibling vanity repo
Trending
Quiet since July.about the whole repository
Who's talking about akash-network/node
- akash-network/provider“fix: 295: Shell access to a SHM mounted workload”GitHub · Jul 21, 2026 · 1 reactions
- sotskov-do/lava-specs“feat(spec): add Akash chain spec”GitHub · Jul 5, 2026
- akash-network/support“audit: scope AllProvidersAttributes and AuditorAttributes pagination to provider prefix”GitHub · Jun 8, 2026
- akash-network/support“audit: scope AllProvidersAttributes and AuditorAttributes pagination to provider prefix”GitHub · Jun 8, 2026
- overlock-network/provider-akash“Migrate provider to chain-sdk for Akash node v2 / sandbox-2 compatibility”GitHub · Apr 29, 2026
The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 17
Talked about on GitHub (17 times).
On GitHub · 17
- Jul 21, 2026fix: 295: Shell access to a SHM mounted workload — akash-network/provider1 reaction · 1 comment
- Jul 5, 2026feat(spec): add Akash chain spec — sotskov-do/lava-specs0 reactions · 8 comments
- Jun 8, 2026audit: scope AllProvidersAttributes and AuditorAttributes pagination to provider prefix — akash-network/support0 reactions
- Jun 8, 2026audit: scope AllProvidersAttributes and AuditorAttributes pagination to provider prefix — akash-network/support0 reactions
- Apr 29, 2026Migrate provider to chain-sdk for Akash node v2 / sandbox-2 compatibility — overlock-network/provider-akash0 reactions
12 more on GitHub
- Jan 7, 2026refactor: moved ErrInternal from node repo and added ABCICode asserti… — akash-network/chain-sdk0 reactions · 1 comment
- Apr 1, 2025provider: fix `autostake` snapshot — akash-network/helm-charts0 reactions · 1 comment
- Jun 25, 2024deps: refactor goreleaser - add static builds with libwasmvm (backport #3157) — cosmos/gaia0 reactions
- Jun 23, 2024deps: refactor goreleaser - add static builds with libwasmvm — cosmos/gaia0 reactions · 1 comment
- May 13, 2024make akash-api a SDK — akash-network/support0 reactions · 4 comments
- Apr 23, 2024Add support for Private Registries in Cloudmos and AkashJS — akash-network/console0 reactions
- Feb 27, 2024GPU ram is not included when parsing SDL in Cloudmos — akash-network/console0 reactions · 1 comment
- Nov 8, 2023Upgrade Akash to v0.26.2 — cosmos/chain-registry0 reactions
- Jun 8, 2023Fix Akash to 0.22.7 for Huckleberry — cosmos/chain-registry0 reactions
- Apr 11, 2023`lease-shell` breaks with `remote server returned 404` once provider service gets restarted (`.manifest.deployments` track breaks as well) — akash-network/support0 reactions · 6 comments
- Jan 24, 2023provider: prometheus exporter - monitor deployments, bids, leases, attributes, ... — akash-network/support0 reactions
- Jan 22, 2023provider: `AKASH_CLUSTER_WAIT_READY_DURATION` code has been removed in akash `v0.16.5-rc0` — akash-network/support0 reactions · 4 comments
In this repository4 other files it gives its agents.
- guidelinesSkill
- setup-envSkill
- build-contractsSkill
- upgrade-changelogSkill
The file
Files
Instructions
Register the current node major version as a vanity URL in the github.com/com/akash-network/vanity repo.
Steps
- Read the major version from
go.modin this repo. Extract the version suffix from the module path (e.g.pkg.akt.dev/node/v2→v2). If the module path has no version suffix (v0/v1), abort — no vanity entry is needed. - Get the current git branch name using
git rev-parse --abbrev-ref HEAD. - Open
vanity/vangen.jsonand check if a repository entry with"prefix": "node/vN"already exists (wherevNis the version from step 1). If it exists, inform the user and abort. - Add a new entry to the
repositoriesarray invanity/vangen.json:
{
"prefix": "node/vN",
"type": "git",
"main": true,
"url": "https://github.com/akash-network/node",
"source": {
"home": "https://github.com/akash-network/node",
"dir": "https://github.com/akash-network/node/tree/BRANCH{/dir}",
"file": "https://github.com/akash-network/node/blob/BRANCH{/dir}/{file}#L{line}"
},
"website": {
"url": "https://github.com/akash-network/node"
}
}Replace vN with the detected version and BRANCH with the detected branch name. Place the entry after the last existing node entry.
- Run
make vangeninvanityto regenerate HTML files. - Verify that
vanity/node/vN/index.htmlwas created and contains the correctgo-importandgo-sourcemeta tags pointing to the detected branch. Also verify that existingvanity/node/index.htmland anyvanity/node/vN/index.htmlis unchanged.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

