You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this was intentional at first, releases of mainline versions on coder/coder happen in parallel with stable ones, which means you can have v2.11.0, then v2.10.3, then v2.11.1, and so on.
This should be fixed, the embeds should also mention whether the release is mainline or stable to avoid confusion from users.
The text was updated successfully, but these errors were encountered:
I'm rewriting this feature in the context of the TypeScript rewrite (#10) and I'm wondering if we really do want to fix this?
Do we really want to publish an announcement every time a mainline version is released?
Another question I had in mind, do we want to publish new versions of our other software? like code-server and envbuilder?
Currently posting every release, will try to differentiate stable from security/patch releases in the future but as seen w/ Cian it's complicated w/ our current way of releasing things.
This has been moved out of the bot in favor of a Zap to avoid having to expose a webhook.
While this was intentional at first, releases of mainline versions on coder/coder happen in parallel with stable ones, which means you can have v2.11.0, then v2.10.3, then v2.11.1, and so on.
This should be fixed, the embeds should also mention whether the release is mainline or stable to avoid confusion from users.
The text was updated successfully, but these errors were encountered: