"tests-passed" is now "latest"

AI-generated summary

david announced that the tests-passed branch is being renamed to latest, aligning with a new versioning strategy for Discourse. While the functionality remains unchanged—code still moves from main to latest after passing tests—the branch name and version suffix have been updated. To ensure a smooth transition, tests-passed is currently maintained as an exact copy of latest, meaning existing configurations will continue to work. However, the default installation has been updated to use latest, and users with manual app.yml configurations specifying tests-passed are advised to update them. david noted that an admin warning for legacy references is planned for the future, once the new versioning system is finalized.

Richie thanked david for the clarification regarding the future warning. jericson asked if this warning had already been implemented, suggesting it might appear in /admin/whats-new. david confirmed that no warning has been added yet and that tests-passed remains a functional alias. Finally, Ed_S noted that in his forums, the version setting was commented out, so no warning or action was required for those instances.

As part of our work to introduce a new versioning strategy for Discourse, we are renaming the tests-passed branch to latest, and updating the version suffix on that branch from -dev to -latest.

What’s changed?

Functionally, everything remains the same. Changes to Discourse will continue to land in the main branch at first, and then will be promoted to latest once they have passed our extensive suite of tests.

Will this break anything?

No :tada:

Initially, we’re maintaining the tests-passed branch as an exact copy of latest. That means that any systems/configs which are hard-coded to tests-passed will continue to work as before.

The default for the standard install has been updated to use latest. That will automatically take effect on your next container rebuild. If you’ve manually specified version: tests-passed in your app.yml, then you should update it to version: latest.

In the future, we plan to introduce an admin warning for anyone that’s still referencing tests-passed, so that we can ensure everyone is using the new name, and then drop the old branch completely. That’s likely to happen in a few months, after the the rest of the new versioning system has been finalized.

39 Likes

Thank you :sweat_smile:

Did this happen? I’m not actually sure where I’d look for such a warning. Maybe /admin/whats-new?

We haven’t added a warning yet. tests-passed remains a functional alias for latest.

Just to note, in my two forums, I’d used the default, but as such it was commented out:

#version: tests-passed

and so presumably no warning would be needed or given.

1 Like