-
@bherr2
Given automatic processing for 7th release where some file naming schema changed, it appears that we have 2 different versions of ASCT+B table present in "7th release" when there should only…
-
### Describe what should be investigated or refactored
Once Zarf reaches 1.0 we should remove backwards compatibility shims so that the codebase can be cleaner going forward and we make a hard break …
-
This is a bug, given the context versioning which was just discussed on the call. Should be pointing at a versioned context:
https://github.com/uncefact/spec-untp/pull/148/files#diff-4bbcb3ee3ac7bb4…
-
If we complete #37, we can iteratively version as changes are made and automatically update everywhere relevant when necessary.
-
As of v1.0 we're now obliged to make [SemVer MAJOR releases](https://semver.org/#spec-item-8) for "breaking" changes. We should clearly document what events constitute a breaking change, both to help …
-
Hi!
I have a need to track changes of entities in different schemas.
Currently, we define `version_schema` in config :ex_audit. But this forces a single version table in a given schema. Is there…
-
## Open Community Working Meeting 2024-03-25 - 14:00 PT
📺 [See Recording](https://youtu.be/9Ky56fKh1ig)
⏪ [Go To Previous Meeting](https://github.com/json-schema-org/community/issues/672)
Age…
-
This issue tracks the conversation started in https://github.com/TBD54566975/tbdex-kt/pull/33 where `tbdex` was added as a submodule in order to copy over its json schemas. However, we should consider…
-
**Is your feature request related to a problem? Please describe.**
Concept of schema versioning was included to handle migration (applying changes sequentially to roll a schema design forward while k…
-
Same as https://github.com/CenterForOpenScience/SHARE/issues/156
When a schema from a provider changes, we'll need to be able to specify which version of the schema we'd like to normalize against.
F…