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

Release 0.14.6 #282

Closed
ivanperez-keera opened this issue Dec 8, 2023 · 0 comments
Closed

Release 0.14.6 #282

ivanperez-keera opened this issue Dec 8, 2023 · 0 comments
Assignees
Milestone

Comments

@ivanperez-keera
Copy link
Owner

  • Branch off develop.
  • Bump version number in yampa and yampa-test.
  • Document changes.
  • Hide expose-core flag.
  • Push to github.
  • Confirm compilation with Travis CI.
  • Upload candidates to hackage.
  • Fix issues, if any, and repeat process until there are no issues left.
  • Publish release on hackage.
  • Merge into master.
  • Tag version.
  • Merge into develop.
  • Re-introduce expose-core flag.
  • Push all branches and tags.
  • Publish release on github.
@ivanperez-keera ivanperez-keera self-assigned this Dec 8, 2023
@ivanperez-keera ivanperez-keera added this to the 0.14.6 milestone Dec 8, 2023
ivanperez-keera added a commit that referenced this issue Dec 8, 2023
The internal-core flag exposes Yampa's internals. This kind of facility
is discouraged by hackage.

This commit removes that flag altogether before the upload to hackage.
ivanperez-keera added a commit that referenced this issue Dec 8, 2023
Re-introduce flag expose-core to control whether the module
FRP.Yampa.InternalCore should be exposed.

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

No branches or pull requests

1 participant