How to make a release

Releasing

Pacstall

Make sure that the release notes are drafted. This usually includes selecting a name and a color.

Patch	Minor	Major
Shade	New color	New color

Create Pac art for the release.
Edit the manpage template and update it with any information.
Create a branch to your fork from develop.
- Edit pacstall and update the color code (in RGB), the version number, and name.
- Create a file in misc/ called pacstall.md, and copy paste the manpage template into it. Run the command at the bottom of the manpage template page.
- Commit it with the commit messages just like you would do an update on pacstall-programs (upd(pacstall): old -> new) with the backticks.
- Push it.
- Merge it into develop.
Go to the cloned repo (git clone git@github.com:pacstall/pacstall.git) and pull from develop.
git checkout master.
git merge develop && git push origin master.
Publish the release draft.
Create the pacstall deb and attach it with the name pacstall-${version}.deb.
If any features/deprecations happened, look in all our docs and update them accordingly.

Docker

Create the new docker by going into repo-maintain, editing the Dockerfile description, then running:

docker build --no-cache -t pacstall .
docker tag pacstall ghcr.io/pacstall/pacstall:latest
docker tag pacstall ghcr.io/pacstall/pacstall:<version>
docker push ghcr.io/pacstall/pacstall:latest
docker push ghcr.io/pacstall/pacstall:<version>

Push the updated Dockerfile with the same commit used to update pacstall.

Discord

Make an announcement linking to the release page.

🦙 [ If you would like to help make packages available | Tell us about a bug you found | Releases ] 🦙

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

How to make a release

Releasing

Pacstall

Docker

Discord

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Pacstall Wiki

Home

FAQ

Pacscripts

Contributing

Repositories

For devs

Clone this wiki locally