Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Help] How do I get this to work at all? #88

Open
NullVoxPopuli opened this issue May 23, 2020 · 6 comments
Open

[Help] How do I get this to work at all? #88

NullVoxPopuli opened this issue May 23, 2020 · 6 comments

Comments

@NullVoxPopuli
Copy link

NullVoxPopuli commented May 23, 2020

in my package.json

  "release": {
    "plugins": [
      "@semantic-release/commit-analyzer",
      "@semantic-release/release-notes-generator",
      "@semantic-release/changelog",
      "@semantic-release/npm",
      "@semantic-release/github",
      "@semantic-release/git"
    ]
  },

package versions:

$ cat package.json | jq ".devDependencies" | grep semantic
  "@semantic-release/changelog": "^5.0.1",
  "@semantic-release/git": "^9.0.0",
  "semantic-release": "^17.0.7",

repo:
https://github.com/NullVoxPopuli/ember-jsqr
I manually created the change log

C.I. log: https://github.com/NullVoxPopuli/ember-jsqr/runs/702505043?check_suite_focus=true

What's happening:

  • CHANGELOG.md is empty

What I expect

  • CHANGELOG.md to be populated with all my releases and versions, and continue to update as I merge stuff
@NullVoxPopuli
Copy link
Author

I just learned that, according to https://spectrum.chat/semantic-release/general/how-to-rebuild-changelog-from-scratch~347e02df-a8cb-4081-afce-1f4f3dfd908e, back-filling the changelog isn't supported.

I was able to backfill with:

npx standard-changelog --first-release

hopefully semantic-release adds to it

@NullVoxPopuli
Copy link
Author

it doesn't look like standard-changelog is quite the same? look at this generation: https://github.com/NullVoxPopuli/ember-jsqr/blob/master/CHANGELOG.md#0910-2020-05-23
there is a giant header in between minor versions :-\

@abdelrahmanahmed
Copy link

@NullVoxPopuli According to your CI logs , your commit didn't trigger a release because it was not one of (feat,fix), which is acutly the default commit message for triggering a new release, what i can see from your logs that your commit message was chore, thats why there was no new release triggered and no changelog file created.

Regarding the second question, yes thats weird i don't and seeing to tags 0.9.0 twice is definitely wrong, not sure why.

@ifndefdeadmau5
Copy link

This feature seems clearly a missing piece of this plugin

@pflorek
Copy link

pflorek commented May 21, 2021

We are just using npx conventional-changelog-cli -p angular -i .docs/src/changelog.md -s -r 0 in our ci pipeline

@gouravkhator
Copy link

@NullVoxPopuli According to your CI logs , your commit didn't trigger a release because it was not one of (feat,fix).

@abdelrahmanahmed Even I tried with fix or feat commit messages which did generate a github release, but it didn't generate any CHANGELOG.md.

Please refer this sample repo of mine for config files: https://github.com/gouravkhator/temp-git/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants