release-drafter VS SimpleLogin

For releasing or publishing our code automatically, we will use the action Release Drafter

New release drafts are triggered after every commit is pushed to the main staging build. The drafted release (built with release drafter) will contain all the commits added since the previous release and a suggested new version which will follow the Semantic Versioning rules.

I am thinking I would have to create a GitHub release manually and then have a workflow listening on the "Release created" event, which would pull the image with the correct commit sha, tag it with the proper version and push it. Or using something like Release Drafter with a PR-based Git flow.

During 2021, we worked hard to improve it furthermore and add new functionality. We just released the latest version of cookietemple. It now includes (beside other templates for example an advanced C++ template or a Java CLI template) a modern python template using poetry, nox (nox-poetry), automatic docs setup as well as many cool and modern GitHub actions, like ReleaseDrafter (https://github.com/release-drafter/release-drafter).

Every commit pushed to the main branch will trigger a staging build. In addition to this, every commit pushed to the main branch will draft a new release on GitHub with the help of the release drafter.

We are always actively working on the configuration for Renovate and will continue to fine-tune it. Having pull requests created for every upstream version change will also optimise the generation of automated changelogs (using the excellent Release Drafter GitHub Action we were already using on Lagoon).

I wanted to provide a way to be able to easily create release notes, to enhance transparency on what we are delivering. I chose to use a tool called Release Drafter in our workflow. I wanted to configure how labels would be used in every repository, and for that, we standardised all labels across all repositories. I use: docs, dependencies, bug, feature, and maintenance.

release-drafter / release-drafter

>Email aliases, mailing lists, subaddressing and catch-all addresses support.

Another feature that would be nice to have built-in is masked hide-my-email aliases for privacy like the cloaked email services from iCloud, FastMail, SimpleLogin, Cloudflare email routing, etc.[1]

For now, I use the typical aliases addresses in Dovecot but it doesn't hide the real email when replying. Also, creating new aliases in Dovecot-based email systems is very tedious and cumbersome because you have to go through the cPanel interface to create new aliases. (Some suggest using "catchall" to simplify manual creation of new aliases but that's not workable when spam robots constantly send to new random addresses in your domain.) The cPanel/Dovecot aliases also don't have metadata so you can add details on what the alias is for and when it was created.

[1] masked email services

https://support.apple.com/en-us/105078

https://www.fastmail.help/hc/en-us/articles/4406536368911-Ma...

https://simplelogin.io/

https://blog.cloudflare.com/introducing-email-routing

Note that other than Mozilla’s Firefox Relay and Apple’s Hide My Email there's also SimpleLogin: https://simplelogin.io/

Also the Bitwarden password manager has an integration for SimpleLogin.

Have you reported it here? https://github.com/simple-login/app/issues

To accomplish this, first create a SimpleLogin acct by logging in with Proton. Once thats done go to https://app.simplelogin.io/developer and create a website. Give it your authentik URL.

Yes, you can also use aliases with your 10 accounts for unlimited addresses and to conceal real addresses. https://simplelogin.io (or apps for iOS/Droid). Owned by proton. Use your proton credentials to login… simple login is included with some plans.

I know about https://simplelogin.io/ and as far as I know it is used under the hood by ProtonMail to implement the functionality.