-
-
Notifications
You must be signed in to change notification settings - Fork 376
Prepare release 0.63.0
#1747
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
base: master
Are you sure you want to change the base?
Prepare release 0.63.0
#1747
Conversation
dbad96b
to
444638a
Compare
444638a
to
0b34812
Compare
Will merge it tomorrow |
CHANGELOG.md
Outdated
|
||
**Important news and breaking changes** | ||
|
||
- NOTE: As of Prometheus 3.0, UTF-8 strings are valid for metric names and label names. However, for backward compatibility, this release of YACE still uses the old, stricter legacy validation scheme. UTF-8 validation will be enabled with the next version of YACE, thus requiring that your remote destination is compatible with UTF-8 support. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we should make this a feature flag so people can opt-in first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes good point. I'll use less definitive words here and we can have a feature flag in the next release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question about our support policy for UTF-8. Otherwise LGTM.
Signed-off-by: Cristian Greco <[email protected]>
Signed-off-by: Cristian Greco <[email protected]>
ffd37ca
to
debfbd7
Compare
0.63.0 / 2025-09-23
Important news and breaking changes
NOTE: As of Prometheus 3.0, UTF-8 strings are valid for metric names and label names. However, for backward compatibility, this release of YACE still uses the old, stricter legacy validation scheme. UTF-8 validation will be enabled in a feature version of YACE, thus requiring that your remote destination is compatible with UTF-8 support.
BREAKING CHANGE: the AWS SDK v2 is now the default in YACE. Use the flag
aws-sdk-v1
to switch back to SDK v2. Flagaws-sdk-v2
has been removed.NEW FEATURE:
exportAllDataPoints
, enables the inclusion of past metric data points from the CloudWatch response if available.CachingFactory
concurrent usage issues by @andriikushchdebug
flag by @zipkidassociator_logging_test.go
by @cristiangrecoscrape_job
label withjob
by @yduartep