up to date changelog with fixes
#94
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…kages: via the `Npm-Scope` header. See also https://docs.npmjs.com/misc/registry
…kages: via the `Npm-Scope` header. See also https://docs.npmjs.com/misc/registry
…onsequently from the dev deps)
…nd augmenting github issues with an URL.
… output with `-c` on platforms/terminals which are not recognized as color-supporting. (e.g. Windows+msys bash)
# Conflicts: # package-lock.json
…older) due to `const` usage in the code. Discarding antiquated NodeJS support in `changelog` itself now: NodeJS versions 4 and later are supported and CI tested (adjusted TravisCI config accordingly)
…eport anymore: `expect.an.object` is not the correct use: http://chaijs.com/api/bdd/ --> `expect.an('object')`
…uild -2 and before, after having updated to chai 4)
…eport anymore: `expect.an.object` is not the correct use: http://chaijs.com/api/bdd/ --> `expect.an('object')`
# Conflicts: # package-lock.json
…m -rf node_modules; rm -f package-lock.json; npm i`
…pdated since 2013) to chalk-supports module (which is linked from rmp website's has-color entry). Added note to README for Windows users who run into issues around console TTY detection failing on several msys/mingw systems: `-c` vs. `--color`.
…le `assert.isObject()` does what it's supposed to do.
… are in sync with npm releases, at least when they have a 'semver' format, so we collect those alongside the ones produced by the npm registry. This is particularly handy to obtain a complete releases set (CLI: 'all') when a project is worked on via fork + subsequent "scoping" of that package, but that's just one(1) use case; this functionality is also useful for packages which do have releases via git tags, but have not been registered with npm, for example!
- new generated data is appended to the top of an existing file. - the tool searches the local directory for any file matching the 'changelog*' glob search crriterion and picks the first one it finds. When no file is found, 'CHANGELOG.md' is assumed as a default destination. This behaviour ensures that various incantations of the name do not cause any trouble in `-a`-updating, while any newly created CHANGELOG will have a github-friendly name: "CHANGELOG.md"
…of proper OAuth transfer to github
…lint, test, etc.
… (I don't trust the 'single releae changelog entries only'-behaviour yet...)
Some non-open-source npm packages like https://www.npmjs.com/package/bitmovin-player contain repository fields with empty URLs. This commit handles this case which other wise would throw an error.
# Conflicts: # package.json
…S and active NodeJS versions in package.json (>= 8.0)
…me promise as any positive result. - fix: typos in test descriptions - add tests for the fix to prevent regression
…me promise as any positive result. - fix: typos in test descriptions - add tests for the fix to prevent regression # Conflicts: # test/changelog.test.js
# Conflicts: # package-lock.json # package.json # test/changelog.test.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
available on npm as
@gerhobbelt/changelogFixes/addresses these issues & pullreqs:
npm test: unit tests fail for github&npm #43