The automated release is failing 🚨

[dhis2-bot]

🚨 The automated release from the 32.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 32.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 31.1.0 on branch 32.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=32.0.0 <31.1.0 can be published from branch 32.x.

The following commits are responsible for the invalid release:

• fix: return correct landcover class (56c70bc)
• ci: migrate to github actions (ci: migrate to github actions #78) (33bfd7b)
• fix: ee api upgrade (6540532)
• Spiderify cluster fix (Spiderify cluster fix - backport to 2.32 #69) (4a0edf2)
• Remove method call (2eb426b)
• Remove Leaflet.Sync from 2.32 (18f086f)
• Code fix (62f5a32)
• Version bump (d836e60)
• feat: synchronize the view of two maps (feat: synchronize the view of two maps #56) (7dbffe3)
• Colorise polygons according to data value (Colorise polygons according to data value #55) (d558148)
• v32.0.21 (1ea8dbf)
• v32.0.20 (3c3f42b)
• fix: override circle getBounds before map is bound (fix: override circle getBounds before map is bound #54) (481c187)
• Version bump (86f7561)
• Distinguish between fill and stroke color (3cc4681)
• v32.0.19 (3de65d1)
• Merge pull request Feat/layergroup #53 from dhis2/feat/layergroup (f408910)
• chore: remove unused destructured var (4d3be89)
• chore: install dhis2 style configuration and re-style modified files (a682486)
• Merge remote-tracking branch 'origin/master' into feat/layergroup (ca8b2a8)
• fix: fitbounds, on layergroup and in general (0e83006)
• fix: support index re-ordering (20975bc)
• Version bump (301dbdd)
• feat: event polygons (feat: event polygons #52) (c2debad)
• feat: support generic layer group (89d9156)
• Version bump (59f2bdd)
• Layer ordering for WMS layers (Layer ordering for WMS layers #51) (9ae1a35)
• fix: load EarthEngine directly from node_modules browser build (fix: load EarthEngine directly from node_modules browser build #50) (020ea5f)
• Version bump (9c27dd5)
• Version bump (6ff1e52)
• Point and polygon buffers (Point and polygon buffers #49) (f2b27ce)
• Revert to previous EE lib import fix (36a18ec)
• EE import testing (5748fa8)
• Use Imports loaded for EE lib (c7fe951)
• EE dep upgrade (a97eeec)
• Fix/dhis2 6375 (Fix/dhis2 6375 #48) (2879f96)
• chore: add stale config (e4593a4)
• Layer bounds fix (d74a355)
• Layer order fix (65124d9)
• Don't capture clicks for buffers (cc05e02)
• Bug fixes (f0afa0d)
• Don't close search popup on map click (649a85e)
• Only show popup for place search result (238ffeb)
• Map popup close callback (84a5953)
• Version bump (a95b943)
• Refactoring to allow new Maps GL engine (Refactoring to allow new Maps GL engine #45) (e27f1f2)
• Version bump (a180a53)
• Load Google Maps API over https (b1d1409)
• Version bump (b615288)
• Merge pull request GIS API dependency upgrade #44 from dhis2/task/google-maps-upgrade (b8e23be)
• Dependency upgrade (3b44aa3)
• Dependency upgrade and remove package-lock.json (07009a8)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 32.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[dhis2-bot]

🚨 The automated release from the 32.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 32.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 31.1.0 on branch 32.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=32.0.0 <31.1.0 can be published from branch 32.x.

The following commits are responsible for the invalid release:

• fix: revert changes that was not published (a46d202)
• fix: return correct landcover class (56c70bc)
• ci: migrate to github actions (ci: migrate to github actions #78) (33bfd7b)
• fix: ee api upgrade (6540532)
• Spiderify cluster fix (Spiderify cluster fix - backport to 2.32 #69) (4a0edf2)
• Remove method call (2eb426b)
• Remove Leaflet.Sync from 2.32 (18f086f)
• Code fix (62f5a32)
• Version bump (d836e60)
• feat: synchronize the view of two maps (feat: synchronize the view of two maps #56) (7dbffe3)
• Colorise polygons according to data value (Colorise polygons according to data value #55) (d558148)
• v32.0.21 (1ea8dbf)
• v32.0.20 (3c3f42b)
• fix: override circle getBounds before map is bound (fix: override circle getBounds before map is bound #54) (481c187)
• Version bump (86f7561)
• Distinguish between fill and stroke color (3cc4681)
• v32.0.19 (3de65d1)
• Merge pull request Feat/layergroup #53 from dhis2/feat/layergroup (f408910)
• chore: remove unused destructured var (4d3be89)
• chore: install dhis2 style configuration and re-style modified files (a682486)
• Merge remote-tracking branch 'origin/master' into feat/layergroup (ca8b2a8)
• fix: fitbounds, on layergroup and in general (0e83006)
• fix: support index re-ordering (20975bc)
• Version bump (301dbdd)
• feat: event polygons (feat: event polygons #52) (c2debad)
• feat: support generic layer group (89d9156)
• Version bump (59f2bdd)
• Layer ordering for WMS layers (Layer ordering for WMS layers #51) (9ae1a35)
• fix: load EarthEngine directly from node_modules browser build (fix: load EarthEngine directly from node_modules browser build #50) (020ea5f)
• Version bump (9c27dd5)
• Version bump (6ff1e52)
• Point and polygon buffers (Point and polygon buffers #49) (f2b27ce)
• Revert to previous EE lib import fix (36a18ec)
• EE import testing (5748fa8)
• Use Imports loaded for EE lib (c7fe951)
• EE dep upgrade (a97eeec)
• Fix/dhis2 6375 (Fix/dhis2 6375 #48) (2879f96)
• chore: add stale config (e4593a4)
• Layer bounds fix (d74a355)
• Layer order fix (65124d9)
• Don't capture clicks for buffers (cc05e02)
• Bug fixes (f0afa0d)
• Don't close search popup on map click (649a85e)
• Only show popup for place search result (238ffeb)
• Map popup close callback (84a5953)
• Version bump (a95b943)
• Refactoring to allow new Maps GL engine (Refactoring to allow new Maps GL engine #45) (e27f1f2)
• Version bump (a180a53)
• Load Google Maps API over https (b1d1409)
• Version bump (b615288)
• Merge pull request GIS API dependency upgrade #44 from dhis2/task/google-maps-upgrade (b8e23be)
• Dependency upgrade (3b44aa3)
• Dependency upgrade and remove package-lock.json (07009a8)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 32.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[stale]

Hi!

Due to a lack of activity on this issue over time (180 days) it seems to be stale. If still relevant, please provide information that moves it forward, e.g. additional information, a pull request with suggested changes, or a reason to keep it open.

Any activity will keep it open, otherwise it will be closed automatically in 30 days. Thanks! 🤖

[stale]

Automatically closing due to lack of activity. 🤖