chore: update schemas only when a release is done

[vmaerten]

Our schemas are updated as soon as changes are merged into the main branch, but this can be confusing since some features may not be released yet.

To solve this, I followed the same pattern we use for the documentation. The files next-schema.json and next-schema-taskrc.json will be copied to schema.json and schema-taskrc.json during the release process.

[Copilot]

Pull Request Overview

This PR changes the release process so that schema files are only updated during an actual release rather than on every merge into the main branch.

• Introduces constants for the schema and schema-taskrc file source/target paths.
• Implements a new schema() function to copy these files.
• Integrates the schema() call into the release workflow.

Files not reviewed (1)

• website/static/next-schema-taskrc.json: Language not supported

Comments suppressed due to low confidence (1)

cmd/release/main.go:187

• Consider renaming the function 'schema()' to something more descriptive like 'updateSchemas()' to better convey its purpose.

func schema() error {

[pd93]

Nice! This is a good idea. One small suggestion: We could update the CI step that we have for detecting changes to the wrong docs folder so that it detects changes to the wrong schema files too.

[vmaerten]

Done !
I've made the choice to create another job in the workflow. This way we can have a proper error message