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

Break unparsable elm.json more #295

Merged
merged 1 commit into from
Nov 3, 2024
Merged

Break unparsable elm.json more #295

merged 1 commit into from
Nov 3, 2024

Conversation

jfmengels
Copy link
Owner

Supersedes #294

This will prevent dependabot from trying to update it (which I imagine it does because support for comments is improving?)

@lishaduck
Copy link
Contributor

I imagine it does because support for comments is improving?

I assumed that too, but I just looked through it, it like is hasn't changed in over a year (beyond rubcop and sorbet fixes, and it used to shell out to elm if I understood correctly, though I didn't look too closely)

@jfmengels jfmengels force-pushed the break-unparsable-elmjson branch from 3e3a05e to 9814909 Compare November 3, 2024 21:08
@jfmengels
Copy link
Owner Author

Well this passes after clearing the cache (#288 (comment)) 🤷‍♂️

@jfmengels jfmengels merged commit 050ca19 into main Nov 3, 2024
3 checks passed
@jfmengels jfmengels deleted the break-unparsable-elmjson branch November 3, 2024 21:18
@lishaduck
Copy link
Contributor

Oh, I guess it passed b/c it's not considered part of cache key. I'll check.

@lishaduck
Copy link
Contributor

lishaduck commented Nov 3, 2024

Nope, freak accident, I guess.
Turbo didn't cache it.

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