🚀 Feature: Add a --privacy flag for publishConfig > access

[JoshuaKGoldberg]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Overview

Publish configs were added in #465 -> #466. It should be that if you initialize a new repository and add the requisite tokens, publishing should work immediately. But, per https://twitter.com/malloc007/status/1693623834509824120, the lack of access: true means packages might not immediately publish well.

Let's add a --privacy flag that defaults to "public". That way users have control over whether the package is public or private, and it's surfaced in the docs.

Additional Info

Thanks @ryota-murakami for speaking up! ❤️

[ryota-murakami]

@JoshuaKGoldberg I'm sorry, my explanation is lacking.
I have no need --private option.

My issue is I couldn't publish new package via create-typescript-app because provenance disallow publish new package no matter access or private

• This is error message

npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
npm ERR! code EUSAGE
npm ERR! Can't generate provenance for new or private package, you must set `access` to public.

https://github.com/laststance/usd-query/actions/runs/5927145432/job/16070031891#step:9:50

• this is given option. (this is default of crerate-typescript-app, no modify)

  "npm": {
    "publishArgs": ["--provenance --public"]
  }

https://github.com/laststance/usd-query/actions/runs/5927145432/job/16070031891#step:9:50

I passed --public, but --provenance option blocked publish because new package I atemmpt publish.

My understand correctly, this teemplate couldn't ship new package without modify config tempolary.
That's a point to I would say "issue".

[ryota-murakami]

@JoshuaKGoldberg Recently, I've gotten used to npm publish and release-it, and I've come to think that this is not an issue at all.
Can I close it?

[JoshuaKGoldberg]

Sure, works for me!

[JoshuaKGoldberg]

Ah, I actually hit this today:

1. I created a new package
2. I added GitHub and npm tokens
3. Error: Can't generate provenance for new or private package, you must set access to public.

I'll add this feature in after all. 😄

[github-actions]

🎉 This is included in version v1.32.0 🎉

The release is available on:

• GitHub releases
• npm package (@latest dist-tag)

Cheers! 📦🚀