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

feat: alias deprecated field to deprecation info struct #371

Merged
merged 2 commits into from
Jan 9, 2024

Conversation

jooola
Copy link
Member

@jooola jooola commented Jan 9, 2024

Try to mitigate the removal of the deprecated field from the API, by linking the deprecated field value to the deprecation info object.

@jooola jooola requested a review from a team as a code owner January 9, 2024 09:06
@jooola jooola requested review from apricote and phm07 January 9, 2024 09:06
Copy link

codecov bot commented Jan 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (main@f705d45). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #371   +/-   ##
=======================================
  Coverage        ?   76.46%           
=======================================
  Files           ?       32           
  Lines           ?     6726           
  Branches        ?        0           
=======================================
  Hits            ?     5143           
  Misses          ?     1176           
  Partials        ?      407           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@phm07
Copy link
Contributor

phm07 commented Jan 9, 2024

Why do we keep schema.ISO.Deprecated?

@jooola jooola merged commit e961be9 into hetznercloud:main Jan 9, 2024
5 checks passed
@jooola jooola deleted the deprecated-alias branch January 9, 2024 14:16
@jooola jooola added backport release-1.x Open PR against release-1.x with these changes after the PR is merged. and removed backport release-1.x Open PR against release-1.x with these changes after the PR is merged. labels Jan 9, 2024
Copy link
Contributor

github-actions bot commented Jan 9, 2024

The backport to release-1.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-1.x release-1.x
# Navigate to the new working tree
cd .worktrees/backport-release-1.x
# Create a new branch
git switch --create backport-371-to-release-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e961be9615452fc63c4c71e6561d4e86f8e8e95a
# Push it to GitHub
git push --set-upstream origin backport-371-to-release-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-1.x

Then, create a pull request where the base branch is release-1.x and the compare/head branch is backport-371-to-release-1.x.

@jooola
Copy link
Member Author

jooola commented Jan 9, 2024

We cannot back port this change because the goverter change was not implemented in v1, please ignore this warning.

jooola pushed a commit that referenced this pull request Jan 9, 2024
🤖 I have created a release *beep* *boop*
---


##
[2.6.0](v2.5.1...v2.6.0)
(2024-01-09)


### Features

* alias deprecated field to deprecation info struct
([#371](#371))
([e961be9](e961be9))
* **instrumentation:** allow passing in any prometheus.Registerer
([#369](#369))
([0821c07](0821c07))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
jooola added a commit that referenced this pull request Jan 9, 2024
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.

2 participants