Bump phalcon/talon from 0.6.0 to 0.7.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps phalcon/talon from 0.6.0 to 0.7.0.

Release notes

Sourced from phalcon/talon's releases.

v0.7.0

Changed

Added

Fixed

• AbstractUnitTestCase::setUp() now guards its Di::reset() call behind phalconAvailable(), so packages that use the Talon abstract test cases without Phalcon (or without the DI component) no longer hit a fatal Class "Phalcon\Di\Di" not found at setup time - because AbstractUnitTestCase is the root of the hierarchy, every abstract (AbstractServicesTestCase/AbstractDatabaseTestCase/AbstractBrowserTestCase/AbstractFunctionalTestCase) inherits the fix and can be extended without a DI. When Phalcon is available the reset still runs unchanged. #14
• AbstractBrowserTestCase now clears $_SESSION in tearDown() as well as setUp(), so a test that logs a user in no longer leaks that session into a following test that does not reset it itself. The browser fixture session persists across the in-process app rebuilds and Di::reset() does not clear it, which surfaced as a random-order failure of FixtureSmokeTest::testSecuredShowsGuestWithoutSession (it read a sarah session left behind by BrowserTraitTest). #16

Removed

Changelog

Sourced from phalcon/talon's changelog.

0.7.0 (2026-07-10)

Changed

Added

Fixed

• AbstractUnitTestCase::setUp() now guards its Di::reset() call behind phalconAvailable(), so packages that use the Talon abstract test cases without Phalcon (or without the DI component) no longer hit a fatal Class "Phalcon\Di\Di" not found at setup time - because AbstractUnitTestCase is the root of the hierarchy, every abstract (AbstractServicesTestCase/AbstractDatabaseTestCase/AbstractBrowserTestCase/AbstractFunctionalTestCase) inherits the fix and can be extended without a DI. When Phalcon is available the reset still runs unchanged. #14
• AbstractBrowserTestCase now clears $_SESSION in tearDown() as well as setUp(), so a test that logs a user in no longer leaks that session into a following test that does not reset it itself. The browser fixture session persists across the in-process app rebuilds and Di::reset() does not clear it, which surfaced as a random-order failure of FixtureSmokeTest::testSecuredShowsGuestWithoutSession (it read a sarah session left behind by BrowserTraitTest). #16

Removed

Commits

• 7e5da75 Merge pull request #16 from phalcon/T14-di-reset-guard
• db62768 #14 - fixing bug discovered by infection
• 4f3ea7e #14 - updating changelog
• 190bfe3 #14 - adding guard for di reset
• fcf0421 Merge pull request #15 from phalcon/dependabot/composer/phpstan/phpstan-2.2.4
• f924c62 Bump phpstan/phpstan from 2.2.2 to 2.2.4
• 4da99d3 Fixing deprecation warning
• 2aefee5 correcting changelog link
• See full diff in compare view

[github-actions]

Code Metrics Report

	master (2892e42)	#3 (e4bf21a)	+/-
Coverage	100.0%	100.0%	0.0%
Test Execution Time	1s	1s	0s

Details

  |                     | master (2892e42) | #3 (e4bf21a) | +/-  |
  |---------------------|------------------|--------------|------|
  | Coverage            |           100.0% |       100.0% | 0.0% |
  |   Files             |               46 |           46 |    0 |
  |   Lines             |             1228 |         1228 |    0 |
  |   Covered           |             1228 |         1228 |    0 |
  | Test Execution Time |               1s |           1s |   0s |

---

Reported by octocov