You are reading the release notes for ORY Hydra 1.0.0-beta.1. This is the first release of a series of releases geared towards the final ORY Hydra 1.0.0 release.
We tagged this release as beta.1 as a huge changeset is included and we need to verify that new and existing deployments work as intended. As always, all code has been thoroughly tested with unit, integration and e2e (new!) tests, as well as the official OpenID Connect Conformity test suite. We are thus confident, that you can run this release already in production but advise to proceed with caution if you intend on doing so, because:
- There might be issues when upgrading from versions prior to 1.0.0 (e.g. 0.11.x)
- There might be issues related to storage adapters which have not been caught by our integration tests.
- You might need to run database migrations or adapt to breaking changes as we progress towards 1.0.0. For example,
1.0.0-beta.2might require database migrations or have other breaking changes in it's API.
Our primary goal for "getting to 1.0.0" is:
- Ensure that existing deployments can upgrade with as little manual work as possible. Some work (specifically wrt consent) will be required, but we want to keep it as little as possible. For this, we need your help. If you run an existing environment and plan on upgrading, please inform us (e.g. in the chat) about it and notify us of any issues you encounter.
- Become OpenID Connect Certified. While all tests by the OpenID Foundation are passing, we still need to pay for a human to review the tests and our reference deployment.
With the 1.0 release we're also changing how version works in the ORY ecosystem. Until now, other services like ORY Oathkeeper and ORY Keto had their own versioning. This changes from now on and all services will be released under the same version. This implies, that, if a breaking change in one of the services happens, it will also imply an update to the version of all other services, even if there is no apparent change in that version. This will hopefully improve answering the question: "Which service is compatible with which one"?
This versioning will not be applied to our libraries, such as ORY Ladon, ORY Fosite, and others.
Here are some things we think are likely to be addressed before going 1.0:
- We'll add a way to revoke consent and login sessions based on user-id and user-id+client-id.
- ... we don't know yet, but probably improve migrations from older versions?
As always, major changes have been documented in the UPGRADE GUIDE and all patches have been documented in the CHANGELOG. The UPGRADE guide might be incomplete or hard to read. Please excuse that and open issues or PRs where appropriate.
If you have questions that need consulting, just drop us an email at hi@ory.sh.