Skip to content

[eMudra][v0.42.0] Require Go 1.26.10 (CP #454) - #457

Merged
Madhan Raj Mookkandy (madhanrm) merged 1 commit into
releases/v0.42.0from
madhanm/emudhra-v042-moc-20261028
Oct 28, 2026
Merged

Madhan Raj Mookkandy (madhanrm) merged 1 commit into
releases/v0.42.0from
madhanm/emudhra-v042-moc-20261028

Conversation

@madhanrm

Copy link
Copy Markdown
Collaborator

Summary

Cherry-pick the merged eMudra compiler fix to releases/v0.42.0 for subsequent MOC patch-release preparation (ASZ June2026-ASZ). PR preparation only; this does not authorize or start a release.

Changes

  • Require Go 1.26.10 in the module minimum and independently referenced local GoTool pipeline selectors.
  • Preserve the existing Go 1.26 release minor and all release-line dependency/replacement pins. No go.sum, product logic, tags, catalog, or security-policy changes.

Cherry-pick provenance

  • Source PR: [eMudra] Require Go 1.26.10 for moc builds #454
  • Source merge: d5a095c69ae07a652681abeebe1bfdce14353bf8
  • Verified release baseline: f8d7e19a10192da9854f326351b4be83741befe6
  • CP commit: fc54a166a4bcd4ecd6a5ef07896a65fea1835fb9
  • Applied cleanly using git cherry-pick -x with -m 1 for the source merge commit.

Testing

  • PASS: git diff --check; changed YAML parses.
  • PASS: every tracked local GoTool selector is exactly 1.26.10; go.mod parses with minimum 1.26.10; all non-directive module content and go.sum are unchanged.
  • PASS: effective local compiler is go1.26.10 windows/amd64, with GOTOOLCHAIN=local.
  • PASS: go test -count=1 ./pkg/config with Go 1.26.10 (Windows, CGO disabled, offline, readonly modules).
  • Full cross-platform binary builds, lint/static analysis, and CI remain pending. GNU make and MinGW/GCC are unavailable locally. Draft pending required validation; no claim of full green.

Checklist

  • Required build, test, lint, and security checks pass
  • Human review completed
  • Separate MOC hotfix-release authorization obtained after CP merge

Related Work Items

Source work: AB#40301108.

Copilot Context

  • Skills: moc-patch-release (release-branch provenance), pr-creation (isolated worktree and PR preparation).
  • Prompt: "CP eMudra MOC fixes to this release branches and give me the table with links"; "we have to make moc hotfix release after that".
  • Bounded preparation only: no explicit pipeline triggers, merge/vote/autocomplete, SFS, wiki, or catalog changes.
  • Copilot-Session: 851d17a8-4268-4464-8220-1d1fe8bafc20

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

…20261023

[eMudra] Require Go 1.26.10 for moc builds

(cherry picked from commit d5a095c)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 851d17a8-4268-4464-8220-1d1fe8bafc20
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@madhanrm
Madhan Raj Mookkandy (madhanrm) marked this pull request as ready for review October 28, 2026 19:09
@madhanrm

Copy link
Copy Markdown
Collaborator Author

[Copilot] release-v0.42.0-native-gates-clarification

Repository/pipeline owners: please confirm the required native PR-validation suite(s), and the authoritative gate/policy, for releases/v0.42.0.

Fresh investigation found no current-head native builds for moc#457, moccli#383, moc-sdk-for-go#421, wssd-sdk-for-go#409, mochost-sdk-for-go#33, moc-pkg#752, or wmi#197. Exact-target protection/effective rules, inherited rulesets, current GraphQL isRequired, same-target prior PRs, and native pipeline definitions were inspected. No required native gate was established for these seven; pipeline existence alone is not proof of requiredness. WMI's release protection has an empty required-status-context list; the prior same-target moc-pkg native contexts are not marked required.

Please provide the specific required context/suite or explicit PR-validation direction so the missing validation can be queued narrowly. CLA/CodeQL-only success is not being presented as full native build/test/lint validation. No speculative blanket run, release pipeline, tag/catalog change, or release authorization is implied. The cloudagent/nodeagent release PRs had separate same-target required-Build evidence and their initial requests were already correlated; they are not being duplicated.

@madhanrm

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@madhanrm
Madhan Raj Mookkandy (madhanrm) merged commit 098bbed into releases/v0.42.0 Oct 28, 2026
5 checks passed
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.

4 participants