-
Notifications
You must be signed in to change notification settings - Fork 969
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
Ory Kratos v0.8 #2166
Merged
Ory Kratos v0.8 #2166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aeneasr
force-pushed
the
v0.8
branch
2 times, most recently
from
January 21, 2022 14:16
9ce1590
to
f362323
Compare
Codecov Report
@@ Coverage Diff @@
## master #2166 +/- ##
==========================================
+ Coverage 75.27% 75.93% +0.65%
==========================================
Files 294 297 +3
Lines 15651 15905 +254
==========================================
+ Hits 11782 12077 +295
+ Misses 3037 2972 -65
- Partials 832 856 +24
Continue to review full report at Codecov.
|
…_id` (#1964) BREAKING CHANGES: A major issue has been lingering in the configuration for a while. What happens to your identities when you update a schema? The answer was, it depends on the change. If the change is incompatible, some things might break! To resolve this problem we changed the way you define schemas. Instead of having a global `default_schema_url` which developers used to update their schema, you now need to define the `default_schema_id` which must reference schema ID in your config. To update your existing configuration, check out the patch example below: ```patch identity: - default_schema_url: file://stub/identity.schema.json + default_schema_id: default + schemas: + - id: default + url: file://stub/identity.schema.json ``` Ideally, you would version your schema and update the `default_schema_id` with every change to the new version: ```yaml identity: default_schema_id: user_v1 schemas: - id: user_v0 url: file://path/to/user_v0.json - id: user_v1 url: file://path/to/user_v1.json ```
It is now possible to override individual courier email templates using the configuration system! Closes #2054
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.