Skip to content

docs(packaging): describe the stable, edge and nightly channels #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bpapaspyros merged 1 commit into from
Oct 27, 2026
+3 −2
Merged

docs(packaging): describe the stable, edge and nightly channels #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions packaging/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,8 +39,9 @@ archive. If one of its dependencies has not been published yet, `mk-build-deps`
`workspace/build_all.sh` rebuilds the whole set in dependency order. Use it for a new ROS distro, a
new Ubuntu release, or a toolchain change.

Publishing to `nightly` is automatic. Promotion to `stable` is `aptly publish switch`, which moves
a pointer. Never rebuild to promote: a mirror holding `1.0.0` will not fetch a different `1.0.0`.
A release publishes to `stable` and a build of main to `edge`. `nightly` is filled by promotion:
`archive/promote.sh edge nightly` switches it to what `edge` publishes, which moves a pointer and
builds nothing. Never rebuild to promote: a mirror holding `1.0.0` will not fetch a different `1.0.0`.

## Secrets

Expand Down
Loading