Skip to content

Optimize remote store GC flow with pinned timestamps #21530

Optimize remote store GC flow with pinned timestamps

Optimize remote store GC flow with pinned timestamps #21530

Triggered via pull request September 25, 2024 09:57
@gbbafnagbbafna
closed #15943
Status Success
Total duration 14s
Artifacts

backport.yml

on: pull_request_target
Backport
6s
Backport
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Backport
The following actions use a deprecated Node.js version and will be forced to run on node20: VachaShah/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Backport
Unexpected input(s) 'installation_id', valid inputs are ['app_id', 'github_api_url', 'installation_retrieval_mode', 'installation_retrieval_payload', 'permissions', 'private_key', 'repositories', 'revoke']
Backport
Unexpected input(s) 'installation_id', valid inputs are ['app_id', 'github_api_url', 'installation_retrieval_mode', 'installation_retrieval_payload', 'permissions', 'private_key', 'repositories', 'revoke']
Backport
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/