Skip to content

[WIP] Implement caching for release fetching in update command#18719

Closed
Copilot wants to merge 4 commits intomainfrom
copilot/cache-release-fetching-resolution
Closed

[WIP] Implement caching for release fetching in update command#18719
Copilot wants to merge 4 commits intomainfrom
copilot/cache-release-fetching-resolution

Conversation

Copy link
Contributor

Copilot AI commented Feb 27, 2026

  • Explore codebase to understand update command structure
  • Add caching for resolveLatestRelease in update_workflows.go (thread cache through UpdateWorkflowsupdateWorkflowresolveLatestRefresolveLatestRelease)
  • Add caching for getLatestActionRelease in UpdateActions (add local cache map similar to UpdateActionsInWorkflowFiles)
  • Update "Fetching releases..." progress message in update_workflows.go to include repo name
  • Update "Fetching releases..." progress message in update_actions.go to include repo name
  • Update test(s) that call resolveLatestRef directly to pass the new cache parameter
  • Build, lint, format, and tests all pass
  • Code review: no issues found
  • Security scan: no alerts

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI and others added 2 commits February 27, 2026 17:14
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
@pelikhan
Copy link
Contributor

@copilot merge main and recompile. review and simplify

Copilot stopped work on behalf of pelikhan due to an error February 28, 2026 01:28
@pelikhan
Copy link
Contributor

@copilot merge main and recompile. review and simplify

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.

2 participants