-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate cache service v2 #1857
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason why we have these dependencies now in the top level package.json?
@@ -38,6 +38,7 @@ | |||
}, | |||
"dependencies": { | |||
"@actions/core": "^1.10.0", | |||
"@actions/artifact": "^2.1.7", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm hesitant to have cache depend on artifact if it's only for obtaining the tokens from the environment. is there a better package we can move that logic to (core?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally yes. For now, I'm just going to duplicate the logic so that we can decrease the complexity of the rollout
// TODO: Use the feature flag to determine the cache service version | ||
export function getCacheServiceVersion(): string { | ||
return process.env['ACTIONS_CACHE_SERVICE_VERSION'] || 'v1' | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when this is fixed, we should include some logic to check for results env too. we don't want to end up removing the feature flag after ship and attempting to hit v2 in GHES
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix
H |
Upgrading the cache package to integrate with the new cache service backend (cache service v2). Major changes to the API layer are involved with this change but the interfaces are backward compatible. The transition to the new service will undergo gradual rollout and will be seamless to end users.
More context
Deprecation notice for v1 and v2 of actions/cache