Skip to content

chore: Cherry-picked changes from upstream#127

Open
github-actions[bot] wants to merge 1 commit intomainfrom
auto-cherry-pick
Open

chore: Cherry-picked changes from upstream#127
github-actions[bot] wants to merge 1 commit intomainfrom
auto-cherry-pick

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked changes from upstream.

…gging (#233)

* Initial plan

* Add automated release workflows and documentation

Co-authored-by: lukka <681992+lukka@users.noreply.github.com>

* Add release process documentation to README

Co-authored-by: lukka <681992+lukka@users.noreply.github.com>

* Fix code review issues: concurrency, validation, and documentation

Co-authored-by: lukka <681992+lukka@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: lukka <681992+lukka@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor Author

🚀 PR Updated!

The PR has been updated with the latest cherry-picked commits.

@step-security/maintained-actions-dev Please review and approve the changes.

📦 Target Release Version: v4.2.3
📋 Previous Release Version: v4.2.2

⚠️ Completely Skipped Commits Due to only modifying files in: package.json, package-lock.json, yarn.lock, node_modules/, dist/, or .gitignore

  • 1bfad7b462c7bdce9de8baddc4a479a586342f57
  • 822400bf6a9ad495c9edee74e4b8c787e2afaded

❗ Missing Files:

  • RELEASE_PROCESS.md

🛑 Workflow Files (Cannot be auto-applied by GitHub Actions):

  • .github/workflows/auto-release.yml from commit f176ccd3f28bda569c43aae4894f06b2435a3375
  • .github/workflows/sync-latest-and-tag.yml from commit f176ccd3f28bda569c43aae4894f06b2435a3375

❌ Conflicting Files:

  • .latest_cmake_version from commit e7542854e3fe0166dffaba8d1cd565da2496a902
  • src/releases-catalog.ts from commit e7542854e3fe0166dffaba8d1cd565da2496a902

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.

0 participants