chore: release

[github-actions]

🤖 New release

• rustc-demangle: 0.1.25 -> 0.1.26 (✓ API compatible changes)
• rustc-demangle-capi: 0.1.1 -> 0.1.2

Changelog

rustc-demangle

0.1.26 - 2025-07-16

Other

• Add new v0 demangling tags for pattern types
• Do not publish the native-c crate
• Use release-plz for releases
• Add a CI workflow to publish new releases after a tag is pushed

rustc-demangle-capi

0.1.2 - 2025-07-16

Other

• updated the following local packages: rustc-demangle

---

This PR was generated with release-plz.

[oli-obk]

hmm... do we really need a capi bump just because demangle got a bump?

[tgross35]

Unfortunately it's a bit of a quirk of release-plz release-plz/release-plz#1814. Usually when this comes up in other repos, I restore the unneeded crate directory from main and force push the release branch.

[Mark-Simulacrum]

I don't really care either way about the spurious release, but can you say more about what review is needed on this? Do we have the automation setup and this just needs approval and it'll auto publish, or does someone (me? :) need to actually run cargo publish?

[tgross35]

Do we have the automation setup and this just needs approval and it'll auto publish, or does someone (me? :) need to actually run cargo publish?

Tag and publish will run automatically whenever this is merged, I think Oli just wanted you to ack the release.

Since it's a bot-created PR, it does need to be closed and reopened to run CI.