Skip to content

Conversation

@Ndpnt
Copy link
Contributor

@Ndpnt Ndpnt commented Nov 18, 2025

No description provided.

@netlify
Copy link

netlify bot commented Nov 18, 2025

Deploy Preview for open-terms-archive-docs ready!

Name Link
🔨 Latest commit b43b6a8
🔍 Latest deploy log https://app.netlify.com/projects/open-terms-archive-docs/deploys/691dc4dd7792fc0008a5d540
😎 Deploy Preview https://deploy-preview-205--open-terms-archive-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

@clementbiron clementbiron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that you use bold type more frequently than on other pages of the documentation website. It's not blocking, but I don't think it's necessary and it's less harmonious.

Thank for this documentation, it is very useful to explain how technical updates work.

Versions created during technical upgrades are marked with:

- `isTechnicalUpgrade: true` in version metadata
- Commit message specify it by starting by `Apply technical or declaration upgrade on …`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Commit message specify it by starting by `Apply technical or declaration upgrade on `
- Commit message specify it by starting by `Apply technical or declaration upgrade on <service_name>`

@Ndpnt Ndpnt merged commit 5b82499 into main Nov 20, 2025
5 checks passed
@Ndpnt Ndpnt deleted the technical-upgrades branch November 20, 2025 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants