Update sbt-header to 5.11.0

[mzuehlke]

closes: #833

[rossabaker]

This is going to need to be a major version bump of this plugin, I think.

[armanbilge]

Indeed. Should bump the base version appropriately in this PR. Any compelling reasons to make this update?

[mzuehlke]

Correct
I will update the PR to update the base version

[rossabaker]

This update will be necessary for eventual SBT 2 support, I think? I don't think it's urgent in the short term, but needed in the long term.

I'm also contemplating an improvement to sbt-header's SPDX handling. That would be a subsequent release.

[mzuehlke]

As @rossabaker sad, we will need a newer version latest when we want to support sbt 2.
In the meantime it depends if we want to always include updates to all used sbt plugins.
Which would lead to more often base version bumps. Or do this very selectively.

[satorg]

Just checknig – is there anything missing in the pull request that is blocking it from getting merged?

[satorg]

@mzuehlke , could you update your branch and resolve conflicts please?
It looks like your PR is otherwise pretty much ready to go to main.
Thank you!

[mzuehlke]

@satorg I updated the PR

[satorg]

@armanbilge , the PR shows it can’t be merged because your review still requests changes. As far as I can tell, the requested changes have been addressed. Could you take another look and clear it when you have a moment?

[armanbilge]

@satorg thanks. Just to clarify, is there a compelling reason to do a new major version of sbt-tl soon? I know we have a bunch of accumulated update PRs that require breaking bumps, but besides that?

[satorg]

@armanbilge , my honest answer is no: I don't have a compelling reason besides keeping the dependencies up-to-date.

We could fork series/0.9 branch out of main, if bumping the latter up is a concern 🤔

[armanbilge]

Sure, we could make a series/0.9 branch (do you have sufficient perms on this repo to do that?). Or, just keep these PRs on ice for now 😅

[satorg]

do you have sufficient perms on this repo to do that?

I guess, I could create the branch... But someone else's help is needed to configure it and setup CI/CD.

Or, just keep these PRs on ice for now 😅

That's certainly an option. I'm just not sure what the signal whould be for us to un-ice those PRs.
On the other hand, if we could release, say, v0.9.0-M1 and let everyone test it out, then it would defenitely help expedite the migration.

[armanbilge]

I'm just not sure what the signal whould be for us to un-ice those PRs.

We will eventually have to bump to 0.9 for some reason. You can check previous releases for examples of why we decided to bump. That would be the signal :)

then it would defenitely help expedite the migration.

Somewhat. A breaking bump in sbt-tl forces a breaking bump of other plugins in its ecosystem, which is why we try to avoid it.