Skip to content
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

Default to using the latest patch version of shopify_function #5045

Closed
wants to merge 1 commit into from

Conversation

nickwesselman
Copy link
Contributor

I was going to update to use v1.0.3 but shouldn't we just encourage use of the latest patch?

@nickwesselman nickwesselman requested a review from a team as a code owner December 5, 2024 21:36
Copy link
Contributor

github-actions bot commented Dec 5, 2024

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run "pnpm changeset add" to track your changes and include them in the next release CHANGELOG.

@@ -246,7 +246,7 @@ async function uiExtensionInit({

if (templateLanguage === 'javascript') {
await changeIndexFileExtension(directory, srcFileExtension)
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was apparently some auto-linting, I assume I should leave it.

@nickwesselman
Copy link
Contributor Author

@andrewhassan @saulecabrera Any concerns with auto-accepting new patch releases by default here?

Copy link
Contributor

github-actions bot commented Dec 5, 2024

Coverage report

St.
Category Percentage Covered / Total
🟡 Statements 75.28% 8769/11649
🟡 Branches 70.56% 4274/6057
🟡 Functions 75.03% 2293/3056
🟡 Lines
75.83% (+0.01% 🔼)
8291/10934
Show files with reduced coverage 🔻
St.
File Statements Branches Functions Lines
🟢
... / app-event-watcher.ts
93.83% (-1.23% 🔻)
86.49% (-2.7% 🔻)
90.48% 98.61%

Test suite run success

1973 tests passing in 895 suites.

Report generated by 🧪jest coverage report action from 3d8ce6a

Copy link
Member

@saulecabrera saulecabrera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the exact version number was used prior to 1.0, in which it was harder to ensure compatibility guarantees between versions. Now that we've reached 1.0 I think this makes sense.

I'll leave the final approval to @andrewhassan in case he wants to share any feedback.

Copy link
Contributor

@isaacroldan isaacroldan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just need to fix the lint issues

Copy link
Contributor

@andrewhassan andrewhassan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see an issue with using the latest patch version.

@andrewhassan
Copy link
Contributor

I think we also need to update the string here. Perhaps we can extract the version out to a constant?

@andrewhassan
Copy link
Contributor

I've included this in my PR here

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