Dev Diary: Build 20

askvortsov

GitHub Action Consolidation

The initial version of the monorepo had separate GH actions scripts for the frontend/backend of every extension / package. This results in a lot of unnecessary jobs running, which leads to rate limiting. Additionally, we can't have separate "build dist js" jobs for each package. A few thoughts on needed changes:

Frontend jobs should only run on changes to some //js/**/* paths
Backend jobs should ignore changes to the aforementioned //js/**/* paths
All frontend jobs need to be consolidated into one GH workflow, so that we can have one step for building all JS. There's several options for doing this, but my thinking is as follows:
- For each type of check (test build, build, typescript, prettier, type coverage), we'll have Flarum CLI generate a comma-separated list of paths to packages where the checks apply.
- Adjust action-build to support js-path as a comma-separated list. It should then perform the build step for every subdirectory instead of for just one.
- Wrap the typescript, type coverage, and prettier checks into bash for loops.
- Consider combining prettier, typescript, and type coverage under one "static analysis"/"linting" step to avoid duplicating some actions.
- Run no-commit "build" steps before the typescript check, so that changes to dist-typings are taken into account properly.
Reusable workflows need to incorporate fail-fast into their matrix strategy.
We'll keep backend PHP jobs separate for now, as the test suite for every package is different, and has different dependencies. However, this might be worth combining too, eventually.

luceos

Apologies for the lack of updates since this amazing update by askvortsov. Most of our team are caught up with other things momentarily, the release of v1.3 is delayed due to that.

We have a meeting planned to schedule the release of v1.3 and to talk about the next steps.

If you are interested in Flarum and would love to contribute to it, we could seriously need you. There's plenty of stuff to do, even testing the new releases as QA for instance. If you're interested, ping me on Discord (https://flarum.org/discord/).

Justoverclock

If someone want to teach me about qa tests, I can defini

TB54 extension manager is near….developers are working hard 💪🏻

luceos

We have completed QA for the upcoming release of v1.3. The three issues that surfaced from it have been dealt with already. Yesterday the newest changes have been published on this community for better stress testing (yes you are our guinea pigs 🙈 ).

The changelogs have also been completed and mostly consist of fixes. Two of these include improvements to Flarum in handling the full spectrum of Unicode characters in search and slug generation 👏.

We're hoping to be able to release v1.3 soon. Stay tuned!

Hari

luceos Unicode characters in search and slug generation 👏.

I feel so satisfied while reading these lines 😍❤️❤️❤️😍😍😍😍❤️😍😍❤️

Hari

get ready guys, we can expect v1.3 anytime!

luceos

Hari on top of things I see 😉

We still have a few things to finish before being able to publish v1.3 like the announcement and perhaps an upgrade guide for developers. But I have good faith we can release v1.3 before the end of next week.

luceos

The announcement has been drafted and developer upgrade guide published, but due to some last minute bugs which we already resolved we won't be able to release this week as was originally planned. Yeah I said something else yesterday, but our motto remains "Underpromise, Overdeliver".

Please help us test this release by posting under the Test Posting tag. If you encounter any issues please report them under Support with a subject prefix with v1.3 so that we can hop onto them before next week and ship v1.3 to you without further delays.

Enjoy your weekend everyone!

Hari

askvortsov luceos discuss is currently running v1.3? 🤔

If that is the case telugu slug generation is not working

https://discuss.flarum.org/d/30796

Telugu search is working flawlessly ✅

CyberGene

With 1.2 I reported a few bugs (with extensions mostly and one with Flarum core) due to installation in sub-folders. I hope you can also test with such a forum somewhere too before releasing it.

luceos

We are aware of the notification dropdown being broken.

edit; fixed 😉

Hari

New package manager 🔥😍🔥😍🔥😍😍🔥
we don't need access to ssh anymore 😍

run global update feature 🔥

luceos

Hari that isn't stable yet and not ready for release.

CyberGene

Will this release be fully compatible with PHP 8.1? Without generating some warning messages that fill-up the log (what I had experienced with 1.2 and had to downgrade to PHP 8.0)

luceos

CyberGene yes.