Release v4.2.0

[robbot006]

This is a draft of changelog for the v4.2.0 release.
Here you can find all related translations changes: v4.1.0...master.

⚠️ Do not merge this pull request manually ⚠️

You should approve this pull request instead. After approving, I will automatically update it (release date needs to be adjusted), merge, and tag a new release. You can read more about the process on forum.

Show release notes preview

v4.2.0

Modifications générales:

• Mise à jour des traductions du noyau de Flarum.

Prise en charge de nouvelles extensions:

• blomstra/oauth-apple
• blomstra/turnstile
• blomstra/web3
• clarkwinkelmann/flarum-ext-money-rewards
• clarkwinkelmann/flarum-ext-money-to-all
• datlechin/flarum-birthdays-widget
• finteger/ratings
• ianm/log-viewer
• ianm/oauth-line
• ianm/oauth-twitch
• jeromegillard/map
• justoverclock/discussion-tags
• justoverclock/staff-members-widget
• vlssu/flarum-cravatar
• ziiven/flarum-daily-check-in
• ziiven/flarum-post-number

Mise à jour des traductions de certaines extensions:

• blessing/flarum-oauth-client
• blomstra/payments
• clarkwinkelmann/flarum-ext-scout
• datitisev/flarum-backup
• datlechin/flarum-birthdays
• datlechin/flarum-signup-button
• flamarkt/backoffice
• flamarkt/taxonomies
• flarum/akismet
• flarum/mentions
• flarum/statistics
• fof/gamification
• fof/geoip
• fof/oauth
• fof/passport
• fof/upload
• hehongyuanlove/flarum-auth-qq
• justoverclock/discussion-info
• kilowhat/flarum-ext-custom-paths
• kilowhat/flarum-ext-wordpress
• kyrne/websocket
• maicol07/flarum-oidc-client
• maicol07/flarum-ext-sso
• nomiscz/flarum-ext-auth-wechat
• spookygames/flarum-ext-auth-keycloak
• v17development/flarum-support
• webbinaro/gpx-preview

Journal de toutes les modifications : v4.1.0...v4.2.0.

[rob006]

@qiaeru Please do no merge these PRs manually, the workflow is explained in the first comment.

[qiaeru]

@qiaeru Please do no merge these PRs manually, the workflow is explained in the first comment.

Yeah I forgot to not delete the release/master branch after the merge, my bad. 😵

[rob006]

Yeah I forgot to not delete the release/master branch after the merge, my bad. dizzy_face

If you merge this PR manually, you need to delete this branch. In other case bot still will be pushing to old branch and it may result some conflicts with new PR (or it may never open new PR - I never tested this). But you should not merge this PR in the first place - just approve it and bot will handle the rest of release process.

[qiaeru]

Yeah I forgot to not delete the release/master branch after the merge, my bad. dizzy_face

If you merge this PR manually, you need to delete this branch. In other case bot still will be pushing to old branch and it may result some conflicts with new PR (or it may never open new PR - I never tested this). But you should not merge this PR in the first place - just approve it and bot will handle the rest of release process.

Yep, I reviewed and approved the PR, I didn't merged it manually, but I deleted the branch before the bot did it. My bad. I will wait in the future, like previous releases.

[rob006]

Yep, I reviewed and approved the PR, I didn't merged it manually, but I deleted the branch before the bot did it. My bad. I will wait in the future, like previous releases.

Are you sure? According to timeline you merged this PR manually without review:

Are you sure you did not confused some options :P.

[qiaeru]

Yep I'm pretty sure. I clicked to review, to approve, then I deleted manually the branch. But heh I'm tired so I don't trust my brain anymore, the timeline don't lie. 😁

Sorry anyway!

[rob006]

If you have any idea how to improve this workflow, I'm open for suggestions. You're not the first person who merged PR instead of approving it, so this is real UX problem, but I don't see an easy option to block manual merges. :/

[qiaeru]

No that's fine, you documented it very well. Translators are not very smart that's all. 😊