chore: release

[github-actions]

🤖 New release

• phper-sys: 0.15.0 -> 0.15.1 (✓ API compatible changes)
• phper-build: 0.15.0 -> 0.15.1
• phper-alloc: 0.15.0 -> 0.15.1
• phper-macros: 0.15.0 -> 0.15.1
• phper: 0.15.1 -> 0.16.0 (⚠ API breaking changes)
• phper-test: 0.15.0 -> 0.15.1 (✓ API compatible changes)
• phper-doc: 0.15.0 -> 0.15.1 (✓ API compatible changes)

⚠ phper breaking changes

--- failure function_missing: pub fn removed or renamed ---

Description:
A publicly-visible function cannot be imported by its prior path. A `pub use` may have been removed, or the function itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/function_missing.ron

Failed in:
  function phper::classes::iterator_class, previously in file /tmp/.tmp0feeKg/phper/src/classes.rs:40
  function phper::classes::array_access_class, previously in file /tmp/.tmp0feeKg/phper/src/classes.rs:46

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/inherent_method_missing.ron

Failed in:
  ReturnType::by_val, previously in file /tmp/.tmp0feeKg/phper/src/functions.rs:366
  ClassEntity::bind_class, previously in file /tmp/.tmp0feeKg/phper/src/classes.rs:720
  Argument::by_val, previously in file /tmp/.tmp0feeKg/phper/src/functions.rs:316
  Argument::by_val_optional, previously in file /tmp/.tmp0feeKg/phper/src/functions.rs:336
  Argument::by_ref_optional, previously in file /tmp/.tmp0feeKg/phper/src/functions.rs:346
  InterfaceEntity::bind_interface, previously in file /tmp/.tmp0feeKg/phper/src/classes.rs:835

--- failure method_requires_different_generic_type_params: method now requires a different number of generic type parameters ---

Description:
A method now requires a different number of generic type parameters than it used to. Uses of this method that supplied the previous number of generic types will be broken.
        ref: https://doc.rust-lang.org/reference/items/generics.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/method_requires_different_generic_type_params.ron

Failed in:
  phper::classes::ClassEntity::extends takes 1 generic types instead of 0, in /tmp/.tmpYLIbFz/phper/phper/src/classes.rs:610

Changelog

phper-sys

0.15.1 - 2025-04-03

Other

• [breaking] add argument and return value type-hints (#187)

phper

0.16.0 - 2025-04-03

Added

• [breaking] rename bind_* to bound_* (#192)

Other

• update readme and remove dep once_cell (#196)
• optimizing extends and implements (#193)
• improve Interface::extends and ClassEntry::extends (#190)
• refactor ClassEntity.implements (#189)
• [breaking] add argument and return value type-hints (#187)

phper-test

0.15.1 - 2025-04-03

Other

• update readme and remove dep once_cell (#196)

phper-doc

0.15.1 - 2025-04-03

Other

• test and document co-dependent classes (#194)
• improve Interface::extends and ClassEntry::extends (#190)
• refactor ClassEntity.implements (#189)
• [breaking] add argument and return value type-hints (#187)

---

This PR was generated with release-plz.

[jmjoy]

@brettmc It's just a test for release-plz. If you want to release it, I can merge it :-)

[brettmc]

It's just a test for release-plz. If you want to release it, I can merge it :-)

I would like to see a 16.0 release, I think this is a good batch of work and I don't have any more changes right now.

I really like how it reports on the breaking changes, that is amazing.

[jmjoy]

I would like to see a 16.0 release, I think this is a good batch of work and I don't have any more changes right now.

I really like how it reports on the breaking changes, that is amazing.

Actually, I don't really like version numbers that jump too drastically; a steady, step-by-step approach is better.