Comments (17)
And published: https://hackage.haskell.org/package/happy-1.20.1 !
The candidate tested well when I downloaded and installed it, and the changelog looked good.
I pushed the tag 1.20.1
to the current HEAD of release-1.20
.
@Ericson2314 : Thanks for fixing the changelog and the .cabal file!
from happy.
@andreasabel Maybe one of us should take a crack at doing github actions on the release-1.20
branch too. I fear this won't be the last time we release a new patch release of it.
from happy.
Let me give it a try.
from happy.
After trying a patched Haskell-CI first, I wrote a CI manually and pushed it to the release-1.20
branch: https://github.com/haskell/happy/actions/runs/4118004445
It basically does make sdist && cabal build
(and runs the tests) on a fresh system with a ubuntu-released happy
preinstalled.
It could be improved by saving the generated tarball as artifact and then installing happy
from this tarball in a subsequent job on a fresh system. This way, we could verify bootstrapping.
from happy.
Ok, hope this is done now, happy-1.20.1.1
is out. I pushed the tag 1.20.1.1 to the current HEAD of release-1.20.
Note to myself on how to release happy-1.20
:
make sdist-test
- Upload the thus generated tarball.
;-)
from happy.
Thanks so much, @andreasabel!
from happy.
@Ericson2314 : What do you think? Would you be willing and able to do this soon?
It would help the Haskell community to prepare for GHC 9.6. E.g. testing BNFC on 9.6 is currently stuck on happy
.
from happy.
@Ericson2314 : I can also do it myself if you add me on Hackage: https://hackage.haskell.org/package/happy/maintainers/edit
from happy.
I can also do it myself if you add me on Hackage
Thank you. I added you to the maintainers.
from happy.
Oh I am sorry I missed this.
from happy.
@Ericson2314 started work on this, so I won't interfere:
from happy.
@andreasabel I am not sure why that CI is failing but I also think it's fine if we make the release before merging it back into master.
I went to bed not having done that yet, and to make up for my tardiness I'll gladly do it myself today, but I don't want you to think me being slow => me wanting to do the release myself. You should certainly be fully empowered to not have to wait for me! (And hopefully now you have all the perms so that is indeed the case.)
from happy.
To test my new capabilities I uploaded a candidate: https://hackage.haskell.org/package/happy-1.20.1/candidate
from happy.
@andreasabel thank you for doing the main work and keep on top of things!
from happy.
So I botched this job...
Here is a new candidate: https://hackage.haskell.org/package/happy-1.20.1.1/candidate
This was generated with make sdist
rather then just cabal sdist
.
The candidate tested well when I downloaded and installed it,
I guess my tests were not stringent enough, since I have a happy
in my PATH on my system. Thus, bootstrapping was not tested.
from happy.
Thank you!
from happy.
It could be improved by saving the generated tarball as artifact and then installing
happy
from this tarball in a subsequent job on a fresh system.
I implemented this and pushed: https://github.com/haskell/happy/actions/runs/4118983519
The CI now implicitly explains how to distribute happy (if you read it carefully) and verifies it for GHC versions 8 and 9. (GHC 7 bindists aren't reliably available on recent Ubuntu.)
from happy.
Related Issues (20)
- Not-unreasonable grammar takes 17min to compile with GHC2021 HOT 3
- Is there a way to revise broken build-plans for older `happy`s? HOT 1
- Should `happy-1.21.0` be revised to become unbuildable? HOT 10
- website (bad link) HOT 2
- inclarity in threaded lexer docs leads to confusing failure HOT 3
- Documentation: Constraints on Parser Monad
- Implement "Principled parsing for indentation-sensitive languages" HOT 5
- Build failures with mtl-2.3 HOT 7
- Upload packages to hackage HOT 5
- Split up CLI into packages
- Incremental parsing
- Internal Happy errors are not helpful
- Idea: Backend for generating railroad diagrams HOT 3
- Build failure in happy-1.20.1 HOT 23
- Support LLVM >=14 HOT 1
- haskell-src-exts: Name mismatch in signature and definition HOT 2
- Readthedocs.org requires a config file for the happy documentation
- Happy refactoring (happy-1.21): either move forward or take it back HOT 6
- Grammar that bison/byacc reports 35 reduce/reduce conflicts but happy none HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from happy.