chore(deps): update github-actions: Bump jdx/mise-action from 2 to 3#6
Merged
scottschreckengaust merged 1 commit intomainfrom Feb 5, 2026
Merged
Conversation
Bumps [jdx/mise-action](https://github.com/jdx/mise-action) from 2 to 3. - [Release notes](https://github.com/jdx/mise-action/releases) - [Changelog](https://github.com/jdx/mise-action/blob/main/CHANGELOG.md) - [Commits](jdx/mise-action@v2...v3) --- updated-dependencies: - dependency-name: jdx/mise-action dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
scottschreckengaust
deleted the
dependabot/github_actions/jdx/mise-action-3
branch
icarthick
added a commit
to icarthick/agent-plugins
that referenced
this pull request
Feb 27, 2026
…gic (Critical Issue awslabs#6) 1. Add explicit retry logic to estimate.md - Specify 3 attempts (up to 2 retries) before fallback - Wait intervals: 1s after attempt 1, 2s after attempt 2 - Clear specification: success vs fallback paths 2. Add user-visible warning for fallback - When awspricing fails: Display 'AWS pricing API unavailable; using cached 2026 rates (±15-25% accuracy)' - Not silent; user sees accuracy degradation - Message included in estimation report 3. Add pricing_source field to estimation.json schema - Track: 'live' vs 'fallback' status - Per-service tracking: which services use live API vs fallback - Message explaining accuracy impact 4. Update SKILL.md error handling - Changed: 'awspricing timeout after 2 retries' - To: 'awspricing unavailable after 3 attempts' - Specified all actions: warning display, fallback use, schema updates Result: Full pricing source transparency + per-service accuracy tracking Build: All linters, manifests, security scans pass ✓ Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
icarthick
added a commit
to icarthick/agent-plugins
that referenced
this pull request
Feb 27, 2026
awslabs#3, awslabs#5, awslabs#6, awslabs#7) 1. Add missing edges field to gcp-resource-clusters.json (Issue awslabs#3) - Problem: output-schema.md example lacked edges array - But: discover-iac.md lists edges as CRITICAL field - And: clustering-algorithm.md includes edges in output - Fix: Added edges array with relationship types to output-schema.md - Fields: from, to, relationship_type 2. Align execution.json risks schema (Issue awslabs#5) - Problem: output-schema.md had 4 fields, execute.md had 3 - output-schema: category, probability, impact, mitigation - execute.md: category, probability, mitigation (missing impact) - Naming: 'data loss' vs 'data_loss' - Fix: Added impact field to execute.md - Fix: Aligned naming to use underscores (data_loss, performance_regression) - Added example with multiple risks 3. Align cluster ID naming format (Issue awslabs#6) - Problem: clustering-algorithm.md used 4-component format with region - But: discover-iac.md used 3-component format without region - clustering-algorithm: {service_category}_{service_type}_{gcp_region}_{sequence} - discover-iac: {type}_{subtype}_{sequence} - Fix: Updated discover-iac.md to use 4-component format - Now: compute_cloudrun_us-central1_001 (includes region) 4. Add missing fields to aws-design.json resource schema (Issue awslabs#7) - Problem: design.md example lacked gcp_config field - output-schema.md Design Resource Schema includes gcp_config - Fix: Added gcp_config with example values (machine_type, zone, boot_disk_size_gb) - Now: Full resource schema includes both GCP and AWS configuration Result: All JSON schemas now consistent across files Build: All linters, manifests, security scans pass ✓ Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps jdx/mise-action from 2 to 3.
Release notes
Sourced from jdx/mise-action's releases.
... (truncated)
Changelog
Sourced from jdx/mise-action's changelog.
... (truncated)
Commits
6d1e696chore: release v3.6.1 (#365)a836e1bRevert "fix(cache): isolate cache keys per working_directory in monorepos" (#...c53b923chore: release v3.6.0 (#342)d3b8e90chore(deps): update actions/upload-artifact action to v6 (#357)b5a5c92chore(deps): update dependency@types/handlebarsto v4.1.0 (#349)54a1650chore(deps): update github/codeql-action digest to 4bdb89f (#362)891faa7fix(cache): isolate cache keys per working_directory in monorepos (#360)23096c7chore(deps): update actions/setup-node digest to 6044e13 (#361)10c27cdchore(deps): lock file maintenance (#358)e53f0d1chore(deps): update actions/setup-node action to v6 (#356)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)