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.

Sign up for GitHub

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

Jump to bottom

[RFC] Automatically bump requirements when updating packages, with type=project or with an option in the configuration #11906

Closed
lyrixx opened this issue Mar 25, 2024 · 3 comments · Fixed by #11942
Closed

[RFC] Automatically bump requirements when updating packages, with type=project or with an option in the configuration #11906

lyrixx opened this issue Mar 25, 2024 · 3 comments · Fixed by #11942
Labels
Feature
Milestone
2.8

Comments

@lyrixx
Copy link
Contributor

lyrixx commented Mar 25, 2024

Hello,

1️⃣ On projects (as opposed on libraries ; "type": "project"), I think we could run automatically composer bump after each composer update

2️⃣ If this is too intrusive, could we at least have a new configuration flag in the composer.json to configure this behavior

    "config": { "bump-after-update": true }

3️⃣ We could even have something in the middle : 2️⃣ + with true as default value. So if someone doesn't want to to bump, they could turn it out
@fredden
Copy link
Contributor

fredden commented Mar 25, 2024

Why should this be a built-in feature of Composer rather than a case of running composer update && composer bump ?

@lyrixx
Copy link
Contributor Author

lyrixx commented Mar 25, 2024

More or less the same arguments each times but:

  1. Some bots does not bump by default, so it would fix it
  2. Some colleagues does not bump some times, so it would fix them
  3. To ensure it's always bumped
  4. To avoid typos
  5. To automate things

@Seldaek Seldaek added this to the Nice To Have milestone Apr 3, 2024
@Seldaek Seldaek added the Feature label Apr 3, 2024
@Seldaek
Copy link
Member

Seldaek commented Apr 3, 2024

IMO ok to have as an optional thing, I don't think I would do this by default as it seems a bit over-reaching.

@carlos-granados carlos-granados mentioned this issue Apr 22, 2024
Merged
@Seldaek Seldaek modified the milestones: Nice To Have, 2.8 Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature
Projects
None yet
Milestone
2.8
Development

Successfully merging a pull request may close this issue.

Add option to run bump after update carlos-granados/composer
3 participants
@Seldaek @fredden @lyrixx