Repository navigation
Conversation
Bumps the actions-core group with 1 update in the / directory: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 4.2.2 to 6.0.3 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v4.2.2...v6.0.3) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions-core ... Signed-off-by: dependabot[bot] <support@github.com>
…evelop/actions-core-e6ee9d7de3 chore(deps): bump actions/checkout from 4.2.2 to 6.0.3 in the actions-core group across 1 directory
resolve_latest relied solely on the GitHub Release `prerelease` boolean, which is not reliable: a -beta/-rc release can be published with the flag unset, then passes the filter and ranks above the latest stable via sort -V (e.g. midaz-sdk-golang/v2 resolved v2.7.0-beta.8 as latest -> false Outdated). Add a tag-name filter to keep only stable vMAJOR.MINOR.PATCH tags.
…ulti-cluster deploy Forward the build.yml helm-dispatch inputs (app_name_prefix, app_name_overrides, dockerhub_org, path_level, build_context_from_working_dir, enable_helm_dispatch, helm_chart, helm_detect_env_changes, helm_values_key_mappings) and the gitops-update.yml multi-cluster inputs (gitops_runner_type, enable_argocd_sync, commit_message_prefix, deploy_in_firmino, deploy_in_clotilde, use_dynamic_mapping, configmap_updates, enable_docker_login) so the gitops/helm plugins can adopt the consolidated go-release model without losing their deploy. gitops_runner_type defaults to firmino-lxc-runners (deploy needs cluster access), which changes the gitops-update runner default from the build runner to firmino.
…ulti-cluster deploy (#433)
|
Caution Review failedPull request was closed or merged during review WalkthroughPins Changesactions/checkout SHA bump
go-release interface expansion and lerian-lib pre-release fix
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related issues
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a Comment |
🔍 PR Validation Summary✅ PR Mergeable — no blocking failures
|
🔍 Lint Analysis
❌ Failures (2)Action Lint
Pinned Actions
|
🛡️ CodeQL Analysis ResultsLanguages analyzed: Found 3 issue(s): 3 Medium
🔍 View full scan logs | 🛡️ Security tab |
GitHub Actions Shared Workflows
Description
Type of Change
feat: New workflow or new input/output/step in an existing workflowfix: Bug fix in a workflow (incorrect behavior, broken step, wrong condition)perf: Performance improvement (e.g. caching, parallelism, reduced steps)refactor: Internal restructuring with no behavior changedocs: Documentation only (README, docs/, inline comments)ci: Changes to self-CI (workflows under.github/workflows/that run on this repo)chore: Dependency bumps, config updates, maintenancetest: Adding or updating testsBREAKING CHANGE: Callers must update their configuration after this PRBreaking Changes
None.
Testing
@this-branchor the beta tagCaller repo / workflow run:
Related Issues
Closes #
Summary by CodeRabbit
Release Notes
Chores
New Features
Bug Fixes