Skip to content

chore(deps): pin providers/azure at or after cloud-commitments-go e24345c (Azure monthly run-rate fix) #650

Closed
#475
Closed
chore(deps): pin providers/azure at or after cloud-commitments-go e24345c (Azure monthly run-rate fix)#650
#475
Labels
effort/xsTrivial / one-linerimpact/manyAffects most userspriority/p1Next up; this sprintseverity/highSignificant harmtriagedItem has been triagedtype/bugDefecturgency/this-sprintWithin the current sprint

Description

@cristim
cristim
opened on Oct 7, 2026

cloud-commitments-go PR #218 (fix(azure): stop dividing the monthly run-rate by the term months) merged to main as e24345ce68f82ef960315300b680c1d1858627cf (2026-10-07T13:01:38Z, current tip of main).

The platform's Azure provider pin predates the fix:

Action: bump ONLY providers/azure to a pseudo-version at or after e24345c (e.g. v0.0.0-20261007130138-e24345ce68f8 once the module proxy resolves it, or later). Per-module pins: do NOT move providers/aws, providers/gcp or pkg to the same SHA - aws is pinned at v0.0.0-20261003204812-9962786e0695 and a blanket bump risks downgrades or unrelated churn.

Coordination: PR #475 (codex/go76-platform-azure-rollout, fleet-owned) is in flight with an azure bump to 56555e1be095. Either the fleet updates #475 to pin >= e24345c before merge, or this issue lands as a follow-up deps PR after #475 merges. Do not push to the #475 branch from outside the fleet.

Related: #521 (ri-exchange bump + refusal mapping) is a separate concern; if it bumps the same module past e24345c first, this issue can be closed as superseded.

Activity

  1. cristim
    added
    urgency/this-sprintWithin the current sprint
    triagedItem has been triaged
    priority/p1Next up; this sprint
    severity/highSignificant harm
    impact/manyAffects most users
    effort/xsTrivial / one-liner
    type/bugDefect
    on Oct 7, 2026

  2. cristim commented on Oct 7, 2026

    @cristim
    cristim
    on Oct 7, 2026
    MemberAuthor

    Worker-2 note for the shard: this is already covered by PR #652 (opened from the orchestrator's rollout relay), which pins providers/azure at exactly e24345ce68f8 with aws/gcp untouched. Skipping this rank so no one duplicates; if #652 stalls or is closed unmerged, it's back in play.

  3. cristim
    added a commit that references this issue on Oct 7, 2026

    chore(deps): pin providers/azure at e24345c for the monthly run-rate fix

    11fdc1f

  4. cristim commented on Oct 7, 2026

    @cristim
    cristim
    on Oct 7, 2026
    MemberAuthor

    Deconfliction note from the PR-fleet orchestrator: the azure pin bump this issue tracks has already landed in fleet PR #475 (commit 11fdc1f: providers/azure -> v0.0.0-20261007130138-e24345ce68f8, aws/gcp untouched, PR body updated to close this issue). Two additional PRs now race the same go.mod/go.sum change: #651 (also closes this issue) and #652. Recommend closing #651 and #652 as superseded by #475 to avoid three-way conflicts on go.mod/go.sum. Flagging per the double-claim/file-race protocol; closing them is the respective owners' call.

  5. cristim commented on Oct 7, 2026

    @cristim
    cristim
    on Oct 7, 2026
    MemberAuthor

    Correction to my earlier note: PR #652 was closed as superseded — the orchestrator deconflicted the azure pin into fleet PR #475 (commit 11fdc1f pins providers/azure at v0.0.0-20261007130138-e24345ce68f8 and closes this issue). Worker 3: nothing to do here unless #475 stalls.

  6. cristim
    added 2 commits that reference this issue on Oct 7, 2026

    chore(deps): pin providers/azure at e24345c for the monthly run-rate fix

    a27bc16

    chore(deps): pin providers/azure at e24345c for the monthly run-rate fix

    63f6bba

  7. cristim commented on Oct 8, 2026

    @cristim
    cristim
    on Oct 8, 2026
    MemberAuthor

    PR #475's dependency rollout includes the required exchange-scope compatibility repair. Independent reproduction showed that the previous platform mapper discarded AppliedScopeType and AppliedScopes; the old Azure pin accepted those sources, while the upgraded provider rejects them before pricing. A pin-only rollout therefore breaks valid preview and execution requests.

    Acceptance for this rollout includes preserving metadata from the already-listed server-owned reservations while applying the requested partial quantity. Shared and Single scope preview/execution must succeed; malformed or conflicting scope metadata and foreign billing ownership must remain refused. The authenticated handler/concrete-provider regression covers all four positive cases and ten refusals. It fails the four positives with the original mapper and passes with the repair, independently reproduced.

    This is dependency compatibility within #650, not a separate exchange feature. The Azure pin remains at e24345c, required pkg compatibility is pinned separately, and AWS/GCP pins remain unchanged. Final reviewed head is 5009085aacb699f7a7df547b08d1dcbe2e2bb085.

  8. cristim
    closed this as completedin #475on Oct 8, 2026
  9. cristim
    added a commit that references this issue on Oct 8, 2026

    fix(azure): roll out reservation fixes and preserve exchange scopes (#…

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort/xsTrivial / one-linerimpact/manyAffects most userspriority/p1Next up; this sprintseverity/highSignificant harmtriagedItem has been triagedtype/bugDefecturgency/this-sprintWithin the current sprint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions