Skip to content

Conversation

chillcicada
Copy link

For yarn classic, "prepublish": "RELEASE=true yarn build" will only take effect on child process for yarn prepublish because here "RELEASE=true" is a shell variable instead of the environment variable. In yarn berry (2+, 3+, 4+), "RELEASE=true" will be promoted to environment variable. while the github ci (ubuntu-lastest) still use yarn classic, so the "prepublish": "RELEASE=true yarn build" will take no effect. There are many solutions:

  • update yarn to berry in ci
  • use cross-env to promote "RELEASE=true" to environment variable for yarn classic
  • set "prepublish": "export RELEASE=true; yarn build" (but this does not work for Windows) or just define the "RELEASE=true" in ci (this commit)

This close #660

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.

The released @taplo/lib is too big, seems RELEASE is not used in CI

1 participant