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

The action regenerates the yarn.lock file and commit it to VCS #252

Open
virtyaluk opened this issue Aug 16, 2024 · 2 comments
Open

The action regenerates the yarn.lock file and commit it to VCS #252

virtyaluk opened this issue Aug 16, 2024 · 2 comments

Comments

@virtyaluk
Copy link

Hello there! Long story short. I use Yarn 4, monorepo, and Yarn Workspaces to manage a handful of web projects in a single code base. Every time this action runs, it updates the package.json file and regenerates the yarn.lock file using Yarn 1 specification (instead of my project's Yarn 4) and commit the changes back to the version control. This is an unwanted side-effect that breaks parts of my code. I'd like to see this action commit only necessary files and avoid touching anything else. Is that possible? Thanks.

image
@phips28
Copy link
Owner

phips28 commented Aug 19, 2024

I would appreciate if you could do a PR for that 🙂

@phips28
Copy link
Owner

phips28 commented Aug 19, 2024

have you tried this: actions/setup-node#904 (comment)

      - name: Enable Corepack
        run: corepack enable

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

No branches or pull requests

2 participants