Bump phalcon/talon from 0.6.0 to 0.7.0

[dependabot]

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)