Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: versioning policy #439

Open
jemgillam opened this issue Jul 31, 2023 · 2 comments
Open

docs: versioning policy #439

jemgillam opened this issue Jul 31, 2023 · 2 comments
Assignees
Labels
Milestone

Comments

@jemgillam
Copy link
Collaborator

Add to policy: Breaking changes to particular parts of dev tooling eg ruru instrumentation don't need a major semver bump

@jemgillam jemgillam added this to the V5 RC milestone Jul 31, 2023
@benjie benjie added the good first issue Good for newcomers label Aug 3, 2023
@benjie
Copy link
Member

benjie commented Aug 3, 2023

Essentially I plan to change the way that explain works, and I'm likely to add to Ruru's functionality over time. The bundled version of Ruru should always work with that version of PostGraphile, but what we're saying is that if we change the format of the configuration or response for the instrumentation payloads then this won't count as a breaking change since it's development only - these features aren't intended for production usage.

@benjie benjie added this to V5.0.0 Oct 4, 2023
@github-project-automation github-project-automation bot moved this to 🌳 Triage in V5.0.0 Oct 4, 2023
@benjie benjie moved this from 🌳 Triage to 🐭 Shrew in V5.0.0 Oct 4, 2023
@benjie
Copy link
Member

benjie commented Feb 8, 2024

This might have been at least partially addressed already? @jemgillam to investigate.

@benjie benjie moved this from 🐭 Shrew to 📝 Docs Improvements in V5.0.0 May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📝 Docs Improvements
Development

No branches or pull requests

2 participants