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

[bot] [main] Automated version update #2230

Closed
wants to merge 1 commit into from

Conversation

prom-op-bot
Copy link
Contributor

Description

This is an automated version and jsonnet dependencies update performed from CI.

Please review the following changelogs to make sure that we don't miss any important
changes before merging this PR.

Unknown component pyrra updated

Configuration of the workflow is located in .github/workflows/versions.yaml.

Type of change

  • NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry


@prom-op-bot prom-op-bot requested a review from a team October 2, 2023 07:39
@prom-op-bot prom-op-bot force-pushed the automated-updates-main branch from 513ce8c to 1ba737a Compare October 2, 2023 07:39
Copy link
Contributor

@philipgough philipgough left a comment

Choose a reason for hiding this comment

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

lgtm cc @metalmatze

@metalmatze
Copy link
Member

Hm, yeah, we don't want to run v0.7 for now. Even though it probably won't break.
Can we somehow pause these updates just for the one dependency, @paulfantom?
Or we simply need to be quicker merging #2229 😂 (I think it'll take some time though)

@paulfantom
Copy link
Member

Just put a static version in

"pyrra": "$(get_version "pyrra-dev/pyrra")"

@paulfantom
Copy link
Member

Alternatively we can just not merge this PR 😅

@metalmatze
Copy link
Member

Just put a static version in

"pyrra": "$(get_version "pyrra-dev/pyrra")"

This is such a workaround I was hoping for. 👍

@metalmatze
Copy link
Member

Let's close this PR for now and then either trigger a new one or wait for the next one to trigger.

@metalmatze metalmatze closed this Oct 5, 2023
@metalmatze
Copy link
Member

#2231

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