#atmos-dev - April 2026

@Andriy Knysh (Cloud Posse) this fixes color handling when using --provenance; manually verified it.

https://github.com/cloudposse/atmos/pull/2281

@Andriy Knysh (Cloud Posse) this is a small one; suppress output from atmos describe affected by default when --upload is passed

https://github.com/cloudposse/atmos/pull/2284

@RB let me know if you have any more PRs you want me to review. I know you have quite a few in flight.

@RB here's the mental hold up on merging this: https://github.com/cloudposse/atmos/pull/2123/changes#r3041795730

@Andriy Knysh (Cloud Posse) this is ready: https://github.com/cloudposse/atmos/pull/1984

@RB you're kicking butt

@Andriy Knysh (Cloud Posse)
https://sweetops.slack.com/archives/CUJPCP1K6/p1775764244063079

cc @Jon Howard

@Igor Rodionov https://github.com/cloudposse/atmos/pull/2306

@Igor Rodionov https://github.com/cloudposse/atmos/pull/2304

@Igor Rodionov https://github.com/cloudposse/atmos/pull/2300

@Andriy Knysh (Cloud Posse) this switches us from <http://autofix.ci|autofix.ci> to native support in atmos pro to commit files that will trigger workflow runs.
https://github.com/cloudposse/atmos/pull/2298

@Andriy Knysh (Cloud Posse) improve error handling for atmos pro, to surface errors to users
https://github.com/cloudposse/atmos/pull/2316

Moving this thread here:
https://github.com/cloudposse/atmos/pull/2309

@Andriy Knysh (Cloud Posse) this was verified by @Dan Hansen https://github.com/cloudposse/atmos/pull/2296

@Andriy Knysh (Cloud Posse) minor one: https://github.com/cloudposse/atmos/pull/2323

Any chance we could get another set of eyes on this bugfix https://github.com/cloudposse/atmos/pull/2184 🥺

@Andriy Knysh (Cloud Posse) added missing redirects https://github.com/cloudposse/atmos/pull/2287

https://github.com/cloudposse/atmos/pull/2129 @Andriy Knysh (Cloud Posse)

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2330

@Alexandre Feblot based on your findings, I pushed some updates to fix the provider aliases.
https://github.com/cloudposse/atmos/pull/2210

can you test with --use-version=2210

Question for you folks. Now that we can create components from upstream modules and even claude our own components, are ALL the cloudposse components still relevant and worth maintaining and creating new components? To push even further back, are there any modules that are so simple that aren't worth migrating to or using?

If any are flagged, will those repos be archived or will their readmes eventually be updated to use the newer/modern approach?

Please review expanding unit tests to atmos

https://github.com/cloudposse/atmos/pull/2173/changes

fix(jit): honor metadata.component subpath for JIT source-provisioned components by zack-is-cool · Pull Request #2371 · cloudposse/atmos

Needs a conceptual look probably, basically found that the metadata.component doesn't do anything with JIT/workdir and this is a proposed fix to that so it works similar to normal vendored components

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2373

Hey guys I have a PR that needs some love 😛
https://github.com/cloudposse/atmos/pull/2379

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2378