Attach .deb artifacts as assets to the release (page) (Bonus: a release DEB repository) #1667

Open
opened 2026-04-15 09:28:29 +00:00 by spaetz · 4 comments
Contributor

Hey Ho, it would be nice to have amd64|arm64 .deb packages as assets on the release pages, right now we only have the bare binaries and source code.

Ideally we would also provide a repository that contains release .deb artifacts rather than nightly .deb builds
(or ideally both, one repo with "just" release artifacts and one with a few nightlies.

Hey Ho, it would be nice to have amd64|arm64 .deb packages as assets on the release pages, right now we only have the bare binaries and source code. Ideally we would also provide a repository that contains release .deb artifacts rather than nightly .deb builds (or ideally both, one repo with "just" release artifacts and one with a few nightlies.
Author
Contributor

P.S. Refer to #1359 which is where the discussion started.

P.S. Refer to https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1359 which is where the discussion started.
Owner

Release packages are already in a different component to dev packages

Release packages are already in a different component to dev packages
Author
Contributor

Ahh, that is interesting, when I go to the release page and click debian packages I end up on a pagethat only describes the "dev" component and lists nightlies.

Ahh, that is interesting, when I go to the[ release page](https://forgejo.ellis.link/continuwuation/continuwuity/releases) and click [debian packages](https://forgejo.ellis.link/continuwuation/-/packages/debian/continuwuity/) I end up on a [page](https://forgejo.ellis.link/continuwuation/-/packages/debian/continuwuity/0.5.7~alpha.1~git20260415.d482e0a-dev)that only describes the "dev" component and lists nightlies.
Author
Contributor

After discussion with @jade: THere is a "stable" component which only contains releases, e.g. https://forgejo.ellis.link/continuwuation/-/packages/debian/continuwuity/0.5.6, but when I click the "debian packages" link on a release page, I end up with a page ONLY describing the "dev" component and offering nightly packages. So, making the release text link to the specific release package would be a great improvement already.

Addmittedly, our install guidelines do describe the stable component repository already (https://continuwuity.org/deploying/debian.html#installation), so perhaps the release text should link to that place?

After discussion with @jade: THere is a "stable" component which only contains releases, e.g. https://forgejo.ellis.link/continuwuation/-/packages/debian/continuwuity/0.5.6, but when I click the "debian packages" link on a release page, I end up with a page ONLY describing the "dev" component and offering nightly packages. So, making the release text link to the specific release package would be a great improvement already. Addmittedly, our install guidelines do describe the stable component repository already (https://continuwuity.org/deploying/debian.html#installation), so perhaps the release text should link to that place?
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity#1667
No description provided.