`v3` branch is not pointing to latest v3 release
Opened this issue · 2 comments
kanadgupta commented
The v3 ref is pointing to v3.3.1 rather than the latest v3.4.0 release, so running this workflow against the v3 ref still yields node12 deprecation warning:
Could someone update the v3 branch to include @mattrothenberg's changes in #86?
I should note that the example in the docs uses v3: https://github.com/githubocto/flat#option-2-manually-create-a-github-actions-workflow-yml-file
Thanks in advance! Big fan of this tool 🙂
mattrothenberg commented
kanadgupta commented
@idan @jaked @mattrothenberg really sorry for the nudge (as an OSS maintainer myself I hate when people do this) but it should only take a few seconds to point the v3 branch to cea5ee4 — could someone help out here?