Feature Request: poetry publish --dry-run

[captn3m0]

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

A --dry-run flag on the poetry publish command will be great. It will let us execute the publish command knowing exactly what is going into the build. As an example, this is what the npm publish --dry-run feature says:

[--dry-run] As of npm@6, does everything publish would do except actually publishing to the registry. Reports the details of what would have been published.

Sample output from npm, just in case

npm publish --dry-run
npm notice
npm notice 📦  [email protected]
npm notice === Tarball Contents ===
npm notice 190B   .editorconfig
npm notice 1.0kB  dist/pincode-0.1.0/LICENSE
npm notice 1.0kB  LICENSE
npm notice 138B   Pipfile
npm notice 491B   dist/pincode-0.1.0/PKG-INFO
npm notice 18.2kB dist/pincode-0.1.0.tar.gz
npm notice 523B   src/index.js
npm notice 747B   package.json
npm notice 1.7kB  README.md
npm notice 459B   dist/pincode-0.1.0/src/pincode/__init__.py
npm notice 459B   src/pincode/__init__.py
npm notice 590B   dist/pincode-0.1.0/setup.py
npm notice 798B   src/pincode/__pycache__/__init__.cpython-38.pyc
npm notice 323B   dist/pincode-0.1.0/pyproject.toml
npm notice 1.0kB  pyproject.toml
npm notice 33.6kB regex.txt
npm notice 17.5kB dist/pincode-0.1.0-py3-none-any.whl
npm notice === Tarball Details ===
npm notice name:          pincode-validator
npm notice version:       1.0.3
npm notice package size:  55.1 kB
npm notice unpacked size: 78.8 kB
npm notice shasum:        cc3eb2cd457f3e672d96949b1e9e1a244912db8d
npm notice integrity:     sha512-HKxJj/kgM2OSj[...]CgeUFYNECuCqw==
npm notice total files:   17
npm notice
+ [email protected]
```</summary>

My current workflow is generating the build, extracting it and inspecting it to see what all files were packaged. Having a dry-run command would improve the UX.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.