Skip to content

Please revert to the previous deploy strategy #464

@bfabio

Description

@bfabio

The new deployment process introduces unnecessary complexity and fragility.

Previously, deployment was rolling: every merge to main went live automatically, and Vercel preview URLs on PRs ensured that patches compiled and worked as expected. This setup enabled quick and safe releases, with a clear workflow for verifying changes.

The new approach makes deployments more manual and error-prone, delaying the release of fixes and features to users. It also increases the risk of inconsistencies going unnoticed.

We no longer need a long-lived branch, that made sense during the refactor phase, but now that the refactored version is live, we need a more agile and incremental release process.

Symptoms of the current state include #441 (point 5: No confusion exists if the deploy is always up to date, and consequentially no need for knowing the version).

Please consider reverting to the previous deploy model.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions