Skip to content
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

Add 1.19.0 changelog #1451

Merged
merged 1 commit into from
Feb 27, 2024
Merged

Add 1.19.0 changelog #1451

merged 1 commit into from
Feb 27, 2024

Conversation

ArthurSens
Copy link
Member

No description provided.

Signed-off-by: Arthur Silva Sens <arthur.sens@coralogix.com>
@SuperQ
Copy link
Member

SuperQ commented Feb 27, 2024

Once this is done, I can mark the Version function in prometheus/common deprecated, cut a release, then remove the circular dependency.

@kakkoyun kakkoyun merged commit 77d4003 into release-1.19 Feb 27, 2024
6 checks passed
@kakkoyun kakkoyun deleted the arthursens/prepare-1.19 branch February 27, 2024 14:33
@@ -1,5 +1,12 @@
## Unreleased

## 1.19.0 / 2023-02-27

The module `prometheus/common v0.48.0` introduced a bug when used together with client_golang. If your project uses client_golang and you want to use `prometheus/common v0.48.0` or higher, please update client_golang to v1.19.0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I find this frustrating, because I can't figure out what the bug is,
even after reading the full list of commits between 1.18 and 1.19.
Could you give a hint?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few constants ceased to exist (or were made private) in common 0.48.0, client_golang would break when trying to access those constants.

The fix was done here: #1448

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and now that you mention I totally agree that this text could be clearer, I'm just not sure if users are interested in such explanation "constant values could not be accessed anymore" 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, linking to the fix is enough information to trace it through.
I would say the root of the thing is prometheus/common#576; some constants were deliberately hidden. I would use the word "incompatibility" rather than "bug".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still haven't merged release-1.19 back to main, so I've raised #1454 and we can get it rephrased :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants