releases
Skill1.4k starsChanged 30 days agoApache-2.0View on GitHub
Plan, validate, cut, or troubleshoot Atmos releases and versioned milestones. Use for stable releases, release candidates, nightly/feature releases, release preview issues, and artifact identity checks.
6 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- LeanMeanCleanApps/CleanLambdaFunctiontheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanWebApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanGraphQLApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanMinimalApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanModelContextProtocoltheir own version, first seen Nov 8, 2026
- nerymurillohnd/the-claude-factorytheir own version, first seen Nov 1, 2026
Who's talking about cloudposse/atmos
- basti-app/basti“homebrew formula to use `brew install basti`”GitHub · Aug 27, 2023 · 4 reactions
- runatlantis/atlantis“Release every time there is a new code change ”GitHub · Dec 24, 2022 · 3 reactions
- dineshba/tf-summarize“Add bump homebrew formula workflow to keep formula updated”GitHub · Sep 19, 2022 · 3 reactions
- cloudposse/terraform-provider-utils“Error: Plugin Did not Respond”GitHub · Dec 12, 2024 · 2 reactions
- NixOS/nixpkgs“atmos: 1.16.0 -> 1.53.0”GitHub · Jan 10, 2024 · 2 reactions
The biggest 5 of 47 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 47
Talked about on GitHub and Hacker News (47 times).
On GitHub · 46
- Aug 27, 2023homebrew formula to use `brew install basti` — basti-app/basti4 reactions
- Dec 24, 2022Release every time there is a new code change — runatlantis/atlantis3 reactions
- Sep 19, 2022Add bump homebrew formula workflow to keep formula updated — dineshba/tf-summarize3 reactions
- Dec 12, 2024Error: Plugin Did not Respond — cloudposse/terraform-provider-utils2 reactions · 3 comments
- Jan 10, 2024atmos: 1.16.0 -> 1.53.0 — NixOS/nixpkgs2 reactions · 2 comments
41 more on GitHub
- Nov 5, 2026[chore] Speed up go cache on Windows GitHub runners — signalfx/splunk-otel-collector1 reaction · 2 comments
- Feb 20, 2026Fix Copilot author detection in mergify rules — cloudposse/.github1 reaction · 2 comments
- Jan 17, 2025`utils_component_config` does not work with `name_template`, requires `name_pattern` — cloudposse/terraform-provider-utils1 reaction
- Oct 17, 2024Adding new --stack parameter — cloudposse/github-action-atmos-affected-stacks1 reaction · 1 comment
- Sep 5, 2024feat: Add Atmos by Cloud Posse — asdf-vm/asdf-plugins1 reaction · 4 comments
- Aug 19, 2024feat: add IAM auth support (required for stack config templating as of atmos `1.86.2`) — cloudposse/github-action-atmos-affected-stacks1 reaction · 1 comment
- May 30, 2022Add a deployment process — jhannah/legislature_calendar1 reaction
- Mar 11, 2022tools: add atmos — shuaibiyy/awesome-tf1 reaction · 1 comment
- Nov 15, 2021atmos 1.3.9 (new formula) — Homebrew/homebrew-core1 reaction · 1 comment
- Nov 10, 2026agent-skills.github.cloudposse.atmos: 1.234.0 → 1.234.1 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.cloudposse.atmos: 1.234.0 → 1.234.1 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.cloudposse.atmos: 1.234.0 → 1.234.1 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-plugins.github.cloudposse.atmos: 1.233.2 → 1.234.0 — sudosubin/agents.nix0 reactions
- Nov 8, 2026claude-code-marketplaces.github.cloudposse.atmos: 1.233.2 → 1.234.0 — sudosubin/agents.nix0 reactions
- Nov 8, 2026agent-skills.github.cloudposse.atmos: 1.233.2 → 1.234.0 — sudosubin/agents.nix0 reactions
- Nov 4, 2026Intermittent windows test failures due to step-security — orcasound/pods-ai0 reactions
- Nov 3, 2026atmos: 1.233.0 -> 1.233.2 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 28, 2026claude-code-plugins.github.cloudposse.atmos: init at 1.233.2 — sudosubin/agents.nix0 reactions
- Oct 28, 2026claude-code-marketplaces.github.cloudposse.atmos: init at 1.233.2 — sudosubin/agents.nix0 reactions
- Oct 25, 2026feat(cloudposse/atmos): trust tagged signing from v1.235.0 — aquaproj/aqua-registry0 reactions · 1 comment
- Oct 25, 2026fix(cloudposse/atmos): update signing identity from v1.233.2 — aquaproj/aqua-registry0 reactions · 2 comments
- Oct 24, 2026agent-skills.github.cloudposse.atmos: 1.233.1 → 1.233.2 — sudosubin/agents.nix0 reactions
- Oct 23, 2026Enroll cloudposse/atmos — anthropics/oss-scanner0 reactions · 3 comments
- Oct 22, 2026atmos: 1.231.0 -> 1.233.0 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 21, 2026agent-skills.github.cloudposse.atmos: 1.233.0 → 1.233.1 — sudosubin/agents.nix0 reactions
- Oct 20, 2026agent-skills.github.cloudposse.atmos: 1.232.0 → 1.233.0 — sudosubin/agents.nix0 reactions
- Oct 16, 2026[Candidate] cloudposse/atmos - large collection (87 SKILL.md files) — ProSkillsMD/proskills0 reactions · 1 comment
- Aug 31, 2026atmos/1.227.0: add package definition for the Atmos CLI — wolfi-dev/os0 reactions
- Aug 30, 2026`import:` in atmos.yaml silently ignored by data sources — Atmos import adapters never registered in the provider binary — cloudposse/terraform-provider-utils0 reactions
- Jun 10, 2026Update Terraform utils to < 1.36.0 (main) — cloudposse/terraform-spacelift-cloud-infrastructure-automation0 reactions · 1 comment
- May 4, 2026Evaluate https://github.com/cloudposse/atmos for opentofu orchastration — GSA-TTS/cloud-sandbox0 reactions
- Mar 11, 2026Improve documentation and add Atmos integration examples — cloudposse/terraform-provider-context0 reactions · 1 comment
- Nov 28, 2025git clone fail when upgraded to git 2.52.0 (latest version as of now) and use command golangci-lint custom — golangci/golangci-lint0 reactions · 2 comments
- Oct 30, 2025Bump github.com/cloudposse/atmos from 1.189.0 to 1.196.0 — cloudposse/terraform-provider-utils0 reactions · 1 comment
- May 13, 2025Plan fails unless VPC isn't already deployed — terraform-aws-modules/terraform-aws-vpc0 reactions · 3 comments
- Jan 21, 2025Addressing Resource Visibility and Pagination Issues — magodo/pipeform0 reactions · 1 comment
- Aug 21, 2024add atmos pro stack locking — cloudposse/github-action-atmos-terraform-apply0 reactions
- Aug 20, 2024DEV-2465: add stack locking — cloudposse/github-action-atmos-terraform-plan0 reactions
- Sep 19, 2023Update Terraform utils to v1.35.0 — MaxymVlasov/renovate-tf-lockfile0 reactions
- Jan 3, 2023Automate releases without a manual PR prior to release — runatlantis/atlantis0 reactions
- Dec 24, 2022Bump homebrew formula upon new releases — runatlantis/atlantis0 reactions
On Hacker News · 1
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- LeanMeanCleanApps/CleanMinimalApi★ 400same name
- LeanMeanCleanApps/CleanGraphQLApi★ 13same name
- LeanMeanCleanApps/CleanWebApi★ 4same name
- LeanMeanCleanApps/CleanModelContextProtocol★ 1same name
- nerymurillohnd/the-claude-factory★ 1same name
- LeanMeanCleanApps/CleanLambdaFunction★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- agent-skills/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/atmos-rules.mdcCursor rule
- atmos-asciicastSkill
- atmos-core-component-developmentSkill
- changelogSkill
- code-hygieneSkill
- component-developmentSkill
- docsSkill
- editionsSkill
- field-testSkill
- fix-allSkill
- fix-logSkill
- gh-stackSkill
- homebrewSkill
- lintSkill
- performance-regressionSkill
- pr-maintenance-loopSkill
- pull-requestSkill
- regression-testSkill
- roadmapSkill
- saySkill
- security-remediateSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- test-coverageSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 5 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run atmos release check from the repository.
- Very specific: line 18
Run atmos release cut. Atmos repeats preflight and asks
- Distinctive: line 20
Never supply confirmation environment variables on behalf of the operator.
- Very specific: line 24
If interrupted, inspect the printed workflow URL/request ID.
- Very specific: line 37
After publication, retry only failed completion/bookkeeping jobs in the original run.
- Distinctive: line 48
After preparation, job names and summaries show the exact reserved tag.
- Very specific: line 54
Every PR needs exactly one of major, minor, patch, no-release.
- Very specific: line 58
Run atmos release milestones ensure to maintain the next three minor slots.
- Very specific: line 62
Run atmos release milestones check to reconcile statuses.
- Distinctive: line 77
Do not edit a draft's version/source in the UI or publish it manually.
- Distinctive: line 80
Do not claim this role boundary is solved by a CI check.
- Very specific: line 84
Use go test -tags=mage ./magefiles/release/..., the local-action test workflow, and the real pinned GoReleaser rehearsal.
- Distinctive: line 88
Keep Go caches enabled. Never publish test releases to production as a test.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Atmos releases
Release version comes exclusively from the lowest open stable-semver milestone.
Labels express compatibility; they never choose the version. Read
docs/prd/release-orchestration.md for architecture, rollout requirements, and limits.
Operator path
- Run
atmos release checkfrom the repository. It selects the next milestone, resolves the exact default-branch SHA, verifies included changes and requires every milestone PR to be merged and present in that SHA. Closed-unmerged PRs block: merge them or move them out. Informational issues may remain open. - Run
atmos release cut. Atmos repeats preflight and asks Do you want to cut X.Y.Z? using its native confirmation UI, default No. Never supply confirmation environment variables on behalf of the operator. - Confirmation binds the version, milestone and SHA. Changes invalidate it. The command dispatches exactly once and follows its uniquely identified run. On success it prints the verified release identity and links.
- If interrupted, inspect the printed workflow URL/request ID. Do not blindly
dispatch another run. Use
atmos release cut --resumefor an unfinished production release. It shows the original tag's source and saved workflow identity for confirmation, reconnects if the run is active, or reruns failed jobs. It never dispatches a replacement workflow or modifies a published release. Conflicts deliberately fail without overwriting tags or assets.
The local cut flow is one Starlark script using native confirmation and shell
steps; Go owns release policy and GitHub operations. Resume requires the original
tag and an unexpired preparation artifact from an unambiguous production run.
It also works before a draft exists if preparation completed and saved its plan.
Missing/expired artifacts, changed eligibility, or conflicting identities require
inspection; do not bypass those checks or rebuild into a partially uploaded draft.
After publication, retry only failed completion/bookkeeping jobs in the original
run; cut --resume deliberately refuses published releases.
atmos release candidate allows unfinished milestone PRs, uses a unique
-rc.N tag (starting at 1 and increasing per version), and leaves the milestone open.
Preparation reserves the number; retries recover the same run's reservation.
Failed builds consume their reserved number. Scheduled nightly and manual
feature workflows use the same verification/publishing pipeline. Feature releases
are dispatched with a PR number and never create release preview issues.
Actions run titles show the release type/version and the CLI correlation ID. After preparation, job names and summaries show the exact reserved tag. Each executed stage summarizes success or failure, checkpoint outcomes, source SHA, and artifact links. A skipped job cannot write a summary.
Milestones and pull requests
- Every PR needs exactly one of
major,minor,patch,no-release. - Except
no-release, every PR needs a versioned milestone. Only the lowest open milestone is merge-eligible. Patch changes fit minor/major milestones; minor changes cannot go into a patch milestone; major changes need a major milestone. - Run
atmos release milestones ensureto maintain the next three minor slots. - Patch and major versions are explicit:
atmos release milestones create vX.Y.Z. - Milestone titles are the bare version (
1.236.0); tags carry thev. Creation accepts either form and stores the bare one; existingvtitles still parse. - Run
atmos release milestones checkto reconcile statuses. TheRelease milestonestatus must be required by repository protection at cutover. - Stable milestone preview issues are informational. Their hidden marker is an association, never authority. Comments/closing an issue do not cut releases.
Workflow boundary
Actions repeats eligibility and authenticates Erik/Andriy by exact numeric user ID, including rerun initiators. There is no dual approval. Build jobs receive OIDC and attestation permissions to sign with GoReleaser and record build provenance, but no release publisher/App credentials. Fresh trusted jobs verify binary version, full source SHA, clean VCS metadata, complete platform/package matrix, hashes, signatures, and attestations before upload and publication. Homebrew and other distribution jobs follow published-release verification. Homebrew builds its own bottles from tagged source; these are not byte-identical to upstream binaries.
Do not edit a draft's version/source in the UI or publish it manually. Direct publishing privileges can bypass workflow checks. Immutable releases prevent post-publication changes only once enabled; they do not authorize publication. Do not claim this role boundary is solved by a CI check.
Verification and rollout
Use go test -tags=mage ./magefiles/release/..., the local-action test workflow, and the real
pinned GoReleaser rehearsal. Local fixtures do not exercise live OIDC signing,
GitHub permissions, immutable publication, or Homebrew's external review/build.
Confirm those in a controlled GitHub rehearsal before enabling production.
Keep Go caches enabled. Never publish test releases to production as a test.
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.

