Releases: Unleash/yggdrasil
unleash-yggdrasil v0.14.0
Chore
- add autoformatting config
New Features
- list known features
Commit Statistics
- 2 commits contributed to the release.
- 6 days passed between releases.
- 2 commits were understood as conventional.
- 2 unique issues were worked on: #156, #157
Commit Details
unleash-yggdrasil v0.13.3
Chore
- ARM ruby build
Bug Fixes
- move wasm engine to handle featureEnabled not feature_enabled
Commit Statistics
- 2 commits contributed to the release over the course of 28 calendar days.
- 32 days passed between releases.
- 2 commits were understood as conventional.
- 2 unique issues were worked on: #145, #149
Commit Details
unleash-yggdrasil v0.13.2
Chore
- make wasm build again
-
chore: make wasm build again
-
chore: make hostname a feature instead
-
fix: put tests behind feature, include env when needed
-
refactor: organize imports slightly differently
-
chore: test all features
-
Bug Fixes
- makes random distribution better distributed
Commit Statistics
- 2 commits contributed to the release over the course of 13 calendar days.
- 14 days passed between releases.
- 2 commits were understood as conventional.
- 2 unique issues were worked on: #141, #144
Commit Details
unleash-yggdrasil v0.13.1
Chore
- add changelog
Commit Statistics
- 4 commits contributed to the release.
- 48 days passed between releases.
- 1 commit was understood as conventional.
- 1 unique issue was worked on: #139
Commit Details
unleash-yggdrasil v0.13.0
Chore
- update unleash-types and chrono
- apply some lints and fixes
Commit Statistics
- 2 commits contributed to the release over the course of 22 calendar days.
- 84 days passed between releases.
- 2 commits were understood as conventional.
- 1 unique issue was worked on: #130
Commit Details
unleash-yggdrasil v0.12.0
Chore
- bump unleash types to 0.12
Commit Statistics
- 1 commit contributed to the release.
- 56 days passed between releases.
- 1 commit was understood as conventional.
- 1 unique issue was worked on: #124
Commit Details
unleash-yggdrasil v0.9.0
Chore
- update types lib
- bump unleash-types and chronos
New Features
- add handling for remote address strategy for subnets and IPv6
- implement hostname strategy in core
- add feature enabled property to variant checks
- Bubble up errors on take state
- Add test for parse error
- Propagate errors in parse date
Bug Fixes
- hostname strategy is now generated correctly and ignores case
- strategies that are broken will now default to false
Commit Statistics
- 9 commits contributed to the release over the course of 62 calendar days.
- 71 days passed between releases.
- 8 commits were understood as conventional.
- 9 unique issues were worked on: #101, #102, #103, #109, #110, #114, #118, #97, #98
Commit Details
view details
- #101
- Implement hostname strategy in core (9613508)
- #102
- Strategies that are broken will now default to false (9e881fc)
- #103
- Hostname strategy is now generated correctly and ignores case (d7158ce)
- #109
- Bump unleash-types and chronos (1611a11)
- #110
- Add handling for remote address strategy for subnets and IPv6 (f4f6ab8)
- #114
- Fix(core)/missing strategy variants no longer impacts other strategies (1f58217)
- #118
- Update types lib (799674d)
- #97
- Bubble up errors on take state (054cac7)
- #98
- Add feature enabled property to variant checks (5225301)
unleash-yggdrasil v0.8.0
Chore
- apply cargo fmt
New Features
- add shouldemitimpressionevents to yggdrasil and .NET wrapper
-
feat: add shouldemitimpressionevents to yggdrasil and .NET wrapper
-
feat: added some impression events tests in dotnet engine
-
- custom strategies in ruby and support in the core engine
Bug Fixes
- make free floating quotes in string operators work correctly
Other
- fix normalized hash result to start from 1 instead of 0
Commit Statistics
- 6 commits contributed to the release over the course of 12 calendar days.
- 13 days passed between releases.
- 5 commits were understood as conventional.
- 5 unique issues were worked on: #56, #63, #65, #75, #80
Commit Details
view details
- #56
- Custom strategies in ruby and support in the core engine (77537e0)
- #63
- Apply cargo fmt (fbfbe32)
- #65
- Fix normalized hash result to start from 1 instead of 0 (adb57f6)
- #75
- Add shouldemitimpressionevents to yggdrasil and .NET wrapper (8c5330b)
- #80
- Make free floating quotes in string operators work correctly (6919241)
- Uncategorized
- Release unleash-yggdrasil v0.7.0 (d9204d6)
unleash-yggdrasil v0.7.0
unleash-yggdrasil v0.6.1
New Features
-
add dependent flags
Description
This PR adds dependent flags to Yggdrasil, complying with the updated client specs.
Regarding these extra points not covered by the spec:
metrics are not called on dependent features :: this is covered and tested
impression events are called on dependent features for easier debugging :: yggdrasil doesn't touch impression events
warning events for missing dependencies are reported once :: yggdrasil doesn't deal with warnings@kwasniew , there is a line in resolveVariant in the Node SDK that checks for parent dependencies being satisfied. What exactly does it do? I tried doing something similar here, but removed it because the tests pass either way. Is this an edge case not covered by the tests, or is it just that the implementations differ here?
(Important) Commits
- feat(#2255): update client specs
- Wip: impl 1 (without updating unleash-types)
- feat(#2255): add test to check that metrics aren't recorded
- feat(#2255): fix assumption in test
- feat(#2255): avoid counting metrics for parents
- feat(#2255): make deps always a vec
- feat(#2255): use unleash-types type for dependency
- feat(#2255): bump unleash-types
- feat(#2255): add test for metrics if parent flag has variants
- Get variant without counting
- feat(#2255): add test to ensure get_variant works
Bug Fixes
- allows current time to be assumed when calculating the context
Commit Statistics
- 3 commits contributed to the release.
- 2 days passed between releases.
- 2 commits were understood as conventional.
- 2 unique issues were worked on: #49, #51