Skip to content

Repo: v6 canary releases workflow is failing #7111

Closed
@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Suggestion

From the v6 canary publish builds (example: https://github.com/typescript-eslint/typescript-eslint/actions/runs/5291845795/jobs/9578445226?pr=5886):

lerna verb publish @typescript-eslint/rule-tester
lerna ERR! EUSAGE Can't generate provenance for new or private package, you must set `access` to public.

Guessing this is from @typescript-eslint/rule-tester being newly added in v6.

My default behavior would be to set "publishConfig": { "access": "public" } in all public facing package.jsons. But @JamesHenry I'll defer to you as the Nx expert, is that the right thing to do?

Metadata

Metadata

Assignees

Labels

repo maintenancethings to do with maintenance of the repo, and not with code/docstriageWaiting for team members to take a look

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions