-
Notifications
You must be signed in to change notification settings - Fork 248
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
Add a changelog #108
Comments
Hey @bluepnume |
Hey @harouny -- sorry for the delay on this, been tied up with a bunch of high priority things. I'll add a changelog soon, but for now the only breaking change with v3 was to do with the Instead of passing a string, the recommended approach is now to pass a DOM element (to which you can attach your own events rather than using things like There's an example here -- https://github.com/krakenjs/xcomponent/blob/master/demo/basic/lightbox/login.js#L14-L113 But let me know if you're using either of those options and I can help you migrate if needed. |
Any news on Changelog? v8 came out with no clues yet |
It will be nice at least to have the PR description and closed issues between releases. Was difficult to link this to this commit in master. |
@bluepnume I do love Zoid, but with no changelog is so difficult to understand what's going on. Why not using @changesets or automatic changelog generators? Open to PR? |
Hi @apuntovanini — definitely open to PRs! |
Hey @bluepnume, would you assign this to me? I think we could create the CHANGELOG differently than what was proposed before. I'd use a Github action to create it so that every time we create a tag, we would automatically generate a Github Release with its changelog attached (like most of the libs are doing nowadays). WDYT? I'd probably use this action. |
That would be great! Thanks @rafaeelaudibert. Assigning to you |
Plenty of people using this now... can't do it cowboy style any more!
The text was updated successfully, but these errors were encountered: