build(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 5am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[Ziettehokiz]

Introducing fees on organization-funded sponsorships
We’re proud that GitHub Sponsors has been fee-free since 2019 and that along with our GitHub Sponsors Matching Fund many developers have received funding for the invaluable work they do.

While we shared at launch that we would eventually introduce fees into the program, we wanted to do so in a way we believed would best support the ecosystem. We’ve worked hard to determine a fee-structure that aligns with the goals of the program while addressing GitHub Sponsors’ costs of processing payments.

As of today, fees will apply to all new sponsorships created by organizations and will depend on which method of payment is used:

Organizations paying by credit card will pay a 6% fee made up of a 3% credit card processing fee and a 3% GitHub service processing fee.
Organizations paying by invoice will be subject only to the 3% GitHub servicing process fee.
For all existing recurring sponsorships made via credit card, these fees will be applied starting June 1, 2023. For those currently made via invoice, fees will not apply to your invoices until your beta agreement expires. Sponsorships funded by individuals remain fee-free.

Learn more about switching to invoiced payments for your GitHub Sponsors payments.

Introducing bulk sponsorships
Organizations sponsoring at scale need better ways to make multiple sponsorships. Last year, GitHub sponsored over 900 of our identified open source dependencies at once and today we’re bringing that tooling to you, too. Bulk sponsorships are built into our GitHub Sponsors Explore page so that you have an easy way to get started with your sponsorable dependencies at hand and they’re now exportable as a CSV, too.

Learn more about bulk sponsorships.

The future of GitHub Sponsors and your feedback
We believe that organization-funded sponsorships are the future of sustainable funding in open source. Approximately 90% of companies use open source in some way today and we’re a long way from seeing that directly translate into financial support. We will continue to make improvements and share stories so that we can remove friction and normalize directly supporting open source dependencies.

Today’s announcements are mostly around the mechanics of payments and checkouts, a small portion of the overall work to be done. We’re also working on providing better ways for maintainers to manage their sponsorships and visibility with their sponsors.

We’re committed to learning as we work towards the goal of making open source careers possible. We love hearing from you in the Community Discussions repository and are grateful to those who help us out in user research and beta testing—thanks so much and stay tuned for more updates!

Tags:
GitHub Sponsors
More on GitHub Sponsors

[github-actions]

🎉 This PR is included in version 2.0.15 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀