Skip to content

Conversation

@services-db
Copy link

@services-db services-db bot commented Jan 15, 2025

Migrate shopify-code-scanner to pull from Artifact Registry

TL;DR

You're currently pulling shopify-code-scanner from GCR, which is going away soon. This PR migrates that reference over to Artifact Registry.


Why is this being asked?

Please check that this PR makes sense, and merge when ready. It should have zero impact.

For further information, please check the issues on your repository. You should have received an issue detailing what's going on. You can also consult the FAQ here: https://github.com/Shopify/gar-migration/blob/main/docs/Artifact_Registry_migration_FAQ.md

What will happen if it doesn't get done within the expected timeframe?

Code scanner will cease to work, preventing your app from building

When does it need to get done?

At the latest, this should be done before 28 Feb 2025.

I don’t think this action item applies to my service. What do I do?

If you believe this action item is not relevant to your Service, you can mark it as not applicable by updating the status of the action item instance to Not applicable in Services DB. Visit the action item instance and click the Not applicable button. Make sure to leave a comment with the reason.

If you change your mind, you can update the status with a reason by navigating to the Action Item Instance page in Services DB. This will reopen the action item instance and the GitHub issue.

I have questions/concerns about this

Please contact the core-commerce-infra team using #proj-gcr-ar-migration.

Your target: liquid-spec
Action Item: https://services.shopify.io/action-items/instances/80814?editStatus=false
Owners: @Shopify/core-storefronts-storefront-platform-planetary-scale-storefronts, @Shopify/liquid-perf, @Shopify/liquid-perf, @Shopify/storefront-platform, @Shopify/storefront-platform-graphql

## TL;DR
You're currently pulling shopify-code-scanner from GCR, which is going away soon. This PR migrates that reference over to Artifact Registry.



---

<h4>Why is this being asked?</h4>
Please check that this PR makes sense, and merge when ready. It should have zero impact.

For further information, please check the issues on your repository. You should have received an issue detailing what's going on. You can also consult the FAQ here: https://github.com/Shopify/gar-migration/blob/main/docs/Artifact_Registry_migration_FAQ.md


<h4>What will happen if it doesn't get done within the expected timeframe?</h4>
Code scanner will cease to work, preventing your app from building

<h4>When does it need to get done?</h4>
At the latest, this should be done before <strong>28 Feb 2025.</strong>



<h4>I don’t think this action item applies to my service. What do I do?</h4>

If you believe this action item is not relevant to your `Service`, you can mark it as not applicable by updating the status of the action item instance to **Not applicable** in Services DB. Visit the [action item instance](https://services.shopify.io/action-items/instances/80814?editStatus=true) and click the **Not applicable** button. Make sure to leave a comment with the reason.

If you change your mind, you can update the status with a reason by navigating to the Action Item Instance page in Services DB. This will reopen the action item instance and the GitHub issue.




<h4>I have questions/concerns about this</h4>

Please contact the **core-commerce-infra** team using #proj-gcr-ar-migration.

**Your target**: [liquid-spec](https://services.shopify.io/services/liquid-spec)
**Action Item**: https://services.shopify.io/action-items/instances/80814?editStatus=false
**Owners**: @Shopify/core-storefronts-storefront-platform-planetary-scale-storefronts, @Shopify/liquid-perf, @Shopify/liquid-perf, @Shopify/storefront-platform, @Shopify/storefront-platform-graphql
@alexcoco alexcoco merged commit d1f1e5c into main Jan 15, 2025
2 of 3 checks passed
@alexcoco alexcoco deleted the migrate_codescanner_to_artifact_registry branch January 15, 2025 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant