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

get changelog generation working with a mono-repo #3

Closed
bcoe opened this issue Feb 20, 2017 · 1 comment
Closed

get changelog generation working with a mono-repo #3

bcoe opened this issue Feb 20, 2017 · 1 comment

Comments

@bcoe
Copy link
Member

bcoe commented Feb 20, 2017

I have an idea about how I'd like to do this, and basically just need to take the time to implement.

I'd like to generate a CHANGELOG for each project in /packages, as versions are released.

I've created a tracking issue here: conventional-changelog/standard-version#156

@bcoe
Copy link
Member Author

bcoe commented Mar 20, 2017

hooray! lerna/lerna#665

@bcoe bcoe closed this as completed Mar 20, 2017
arnabsen pushed a commit to arnabsen/istanbuljs that referenced this issue Feb 20, 2024
…ey-sync

Syncronisation of node types against Estraverse's VisitorKeys
arnabsen pushed a commit to arnabsen/istanbuljs that referenced this issue Feb 20, 2024
Make cobertura report use relative path as filename
arnabsen pushed a commit to arnabsen/istanbuljs that referenced this issue Feb 20, 2024
Restore code that was introduced in nyc 6.5.0 to handle bad source map locations. This fix was originally introduced into nyc's lib/source-map-cache.js, but when nyc transitioned to using istanbul-lib-source-maps this fix went astray.

see original PR: istanbuljs/nyc#255
arnabsen pushed a commit to arnabsen/istanbuljs that referenced this issue Feb 20, 2024
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

1 participant