Skip to content

[UPMERGE] 5.0 -> next#2996

Open
github-actions[bot] wants to merge 21 commits intonextfrom
upmerge/5.0_next
Open

[UPMERGE] 5.0 -> next#2996
github-actions[bot] wants to merge 21 commits intonextfrom
upmerge/5.0_next

Conversation

@github-actions
Copy link
Copy Markdown

This PR has been generated automatically.

Remember! The upmerge should always be merged with using Merge pull request button.

In case of conflicts, please resolve them manually with usign the following commands:

git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/next -m "Resolve conflicts between 5.0 and next"

Copilot AI and others added 21 commits January 29, 2026 11:43
…aintext storage, and missing TTL

Co-authored-by: dpfaffenbauer <5981845+dpfaffenbauer@users.noreply.github.com>
…, immutable datetime handling

Co-authored-by: dpfaffenbauer <5981845+dpfaffenbauer@users.noreply.github.com>
…okens

Co-authored-by: dpfaffenbauer <5981845+dpfaffenbauer@users.noreply.github.com>
Switch pull_request_target to pull_request on workflows that checkout
and execute code from PR forks. Running untrusted fork code with
pull_request_target exposes repository secrets (PIMCORE_SECRET,
PIMCORE_INSTANCE_IDENTIFIER, PIMCORE_PRODUCT_KEY) and GITHUB_TOKEN
write permissions via composer scripts, modified source files, etc.

Affected workflows:
- static.yml, license-check.yaml, packages_bundles.yml,
  packages_components.yml: switched trigger to pull_request
- behat.yml, behat_ui.yml: removed dead pull_request_target checkout
  steps (trigger was already pull_request)
- docs_next.yml: switched to pull_request for consistency

cla-check.yml intentionally kept on pull_request_target — it does
not check out PR code, which is the safe usage pattern.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
[Security] fix pull_request_target workflow injection (pwn request)
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.9 to 1.16.0.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.15.9...v1.16.0)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-version: 1.16.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…reShop/Bundle/FrontendBundle/Resources/assets/follow-redirects-1.16.0

Bump follow-redirects from 1.15.9 to 1.16.0 in /src/CoreShop/Bundle/FrontendBundle/Resources/assets
…-dep

[OrderBundle] remove web2print, not needed anymore
bump symfony constraints to ^6.4 || ^7.3
…tropy

Fix order token generator entropy using CSPRNG and 32-char tokens
…-security

Fix password reset security: user enumeration, weak tokens, plaintext storage, missing TTL
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants