-
It publish to the npm without my output filehere is part of log npm notice === Tarball Contents ===
npm notice 11.4kB LICENSE
npm notice 2.8kB README.md
npm notice 1.8kB package.json
npm notice === Tarball Details === here is my configuration name: Release
on:
push:
branches:
- master
jobs:
semantic-release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Run semantic-release
if: github.event_name == 'push'
run: yarn install && yarn semantic-release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} my {
"debug": true,
"branches": [
"+([0-9])?(.{+([0-9]),x}).x",
"master",
{
"name": "rc"
},
{
"name": "beta",
"prerelease": true
},
{
"name": "alpha",
"prerelease": true
}
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/npm",
"@semantic-release/github"
]
} |
Beta Was this translation helpful? Give feedback.
Answered by
travi
Feb 14, 2022
Replies: 1 comment
-
you need to configure npm itself for the details about what to include in the published package. if you have not done this, npm is likely honoring your |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
fabian4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
you need to configure npm itself for the details about what to include in the published package. if you have not done this, npm is likely honoring your
.gitignore
file. i recommend using thefiles
attribute in thepackage.json
to be explicit about what you want included