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

v37 planning #23911

Closed
5 tasks done
viceice opened this issue Aug 17, 2023 · 12 comments
Closed
5 tasks done

v37 planning #23911

viceice opened this issue Aug 17, 2023 · 12 comments
Assignees
Labels
breaking Breaking change, requires major version bump priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation

Comments

@viceice viceice added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others breaking Breaking change, requires major version bump status:ready status:in-progress Someone is working on implementation and removed status:ready labels Aug 17, 2023
@HonkingGoose
Copy link
Collaborator

@rarkins wanted us to have "config migration via Dependency Dashboard" 1 before making config migration the default behavior. 2

I'll let you maintainers prioritize what's going in v37. 😉

Footnotes

  1. On-demand config migration PRs using Dashboard #19783

  2. Enable config migration by default #16359

@rarkins
Copy link
Collaborator

rarkins commented Aug 22, 2023

I've dropped config migration from default from this list because it's not ready. See #16359 (comment)

@viceice viceice pinned this issue Aug 22, 2023
@rarkins rarkins added the v37 label Sep 22, 2023
@HonkingGoose

This comment was marked as resolved.

@rarkins rarkins changed the title v37 planning v38 planning Sep 29, 2023
@rarkins rarkins added status:requirements Full requirements are not yet known, so implementation should not be started and removed v37 status:in-progress Someone is working on implementation labels Sep 29, 2023
@rarkins
Copy link
Collaborator

rarkins commented Sep 29, 2023

Done!

@rarkins rarkins added status:in-progress Someone is working on implementation and removed status:requirements Full requirements are not yet known, so implementation should not be started labels Oct 1, 2023
@wanisfahmyDE
Copy link

Hi @viceice, we installed the renovatebot app directly in github, how can we know which version is being used and where can we track that?
Asking because a change like mentioned here #23326 (comment) might cause a breaking change for us eventually
Many thanks

@viceice
Copy link
Member Author

viceice commented Oct 27, 2023

we've migration code, so no worries.

renovate version can be seen on mend developer dashboard linked from PR body

@wanisfahmyDE
Copy link

@viceice apologies, I looked everywhere in our mend developer dashboard but I still cannot find it.
Do you mind if you drop a screenshot example?
Thank you <3

@viceice
Copy link
Member Author

viceice commented Oct 27, 2023

you need to check the logs for one of the latest runs

@wanisfahmyDE
Copy link

Found it, thanks alot

@HonkingGoose
Copy link
Collaborator

HonkingGoose commented Nov 13, 2023

@viceice can you put issue #16359 back on your todo list again? 😉 It's currently crossed out.

@rarkins wants to enable the config migration by default in v38, see this comment:

@HonkingGoose
Copy link
Collaborator

@viceice can you update your top post of this issue? Some of your todo's landed in v37. 😉

@viceice viceice mentioned this issue Mar 18, 2024
21 tasks
@viceice viceice changed the title v38 planning v37 planning Mar 18, 2024
@viceice viceice closed this as completed Mar 18, 2024
@viceice
Copy link
Member Author

viceice commented Mar 18, 2024

added a new issue

@viceice viceice unpinned this issue Mar 18, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking Breaking change, requires major version bump priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation
Projects
None yet
Development

No branches or pull requests

7 participants
@JamieMagee @viceice @rarkins @secustor @HonkingGoose @wanisfahmyDE and others