How to version a private project #1312
Replies: 1 comment 4 replies
-
@rawand-faraidun I have private packages working, but it was difficult to set up. What do you see in the logs of your action? I am using Github Packages for my private registry. For Github Packages, I remember I needed to carefully specify the "repository": {
"type": "git",
"url": "git+https://github.com/ORGNAME/REPONAME.git"
}, Here is my - name: Run Changesets
id: changesets
uses: changesets/action@v1
with:
# Call our release script which is defined in the main package.json
publish: npm run release
# Here's what the release script actually does.
# publish: npm run build-all && npx changeset publish
env:
# Changesets needs our Github token. We pass it in an environment variable.
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} My config is probably similar to yours. {
"$schema": "https://unpkg.com/@changesets/config@2.2.0/schema.json",
"changelog": "@changesets/cli/changelog",
"commit": false,
"fixed": [],
"linked": [],
"access": "restricted",
"baseBranch": "main",
"updateInternalDependencies": "patch",
"ignore": []
} I do have a problem that I still need to solve. I think the releases occur when merging to main from my FEATURE branches. I think the version bumps and releases should only occur after merging the VERSION branch to main. |
Beta Was this translation helpful? Give feedback.
-
I have a private project and versioning is so important for me and it is not for npm, I configured changeset to make the changelog and handle the versioning, but it does not make Github releases, here is my configuration
It makes the right pull requests for the versioning everytime i have a changeset markdown, but the problem is as i said the github release is not made
.changeset/config.json
:.github/workflows/release.yml
and here is my
release
script:pnpm run ci && changeset version
And lastly here is my action workflow permissions
Beta Was this translation helpful? Give feedback.
All reactions