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

[cds^8] Node.js - rm legacy config for draft locks #896

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

johannes-vogel
Copy link
Contributor

@johannes-vogel johannes-vogel commented May 6, 2024

@renejeglinsky @smahati What do you think of introducing a different label for next major release? Or should I use this one?

@renejeglinsky renejeglinsky changed the title Node.js - rm dropped legacy config for draft locks [cds^8] Node.js - rm dropped legacy config for draft locks May 6, 2024
@renejeglinsky
Copy link
Contributor

We're thinking about having a convention like I added it to the title now. That maybe makes more sense than lables. But that's not discussed yet, just for the time being. And I think it does the trick :)

@johannes-vogel
Copy link
Contributor Author

We're thinking about having a convention like I added it to the title now. That maybe makes more sense than lables. But that's not discussed yet, just for the time being. And I think it does the trick :)

Either way is fine for me. Just thought it'll be helpful to detect this easily:)

@johannes-vogel johannes-vogel changed the title [cds^8] Node.js - rm dropped legacy config for draft locks [cds^8] Node.js - rm legacy config for draft locks May 6, 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.

None yet

2 participants