# Publish new releases immediately after committing changes

**URL:** https://discuss.privacyguides.net/t/publish-new-releases-immediately-after-committing-changes/39283
**Category:** Site Development
**Created:** 2026-07-22T10:57:41Z
**Posts:** 1

## Post 1 by @yes — 2026-07-22T10:57:41Z

Continuing the discussion from [Cromite still present on PG website despite removal PR on GitHub](https://discuss.privacyguides.net/t/cromite-still-present-on-pg-website-despite-removal-pr-on-github/39194/6):

> [@Cromite still present on PG website despite removal PR on GitHub](https://discuss.privacyguides.net/t/cromite-still-present-on-pg-website-despite-removal-pr-on-github/39194/7):
>
> @jonah Cromite is missing **1233 security fixes** and it is still being recommended.

As we can see here, due to the lack of new releases, Cromite is still recommended on the website.

So I propose that after a commit is made, publish and deploy it immediately so the site is always up-to-date.

Also: [Cromite still present on PG website despite removal PR on GitHub - #10 by privacy.slouchy](https://discuss.privacyguides.net/t/cromite-still-present-on-pg-website-despite-removal-pr-on-github/39194/10)