Skip to content

Update seedsigner-translations submodule to latest dev (9a76a81)#932

Open
Chaitanya-Keyal wants to merge 4 commits into
SeedSigner:devfrom
Chaitanya-Keyal:chore/update-translations-submodule
Open

Update seedsigner-translations submodule to latest dev (9a76a81)#932
Chaitanya-Keyal wants to merge 4 commits into
SeedSigner:devfrom
Chaitanya-Keyal:chore/update-translations-submodule

Conversation

@Chaitanya-Keyal
Copy link
Copy Markdown
Contributor

@Chaitanya-Keyal Chaitanya-Keyal commented May 4, 2026

Description

This PR updates the seedsigner-translations submodule to the latest dev commit (SeedSigner/seedsigner-translations@9a76a81).

Additionally, this PR fixes CI run failures that emerged with this submodule update. In recent changes to the seedsigner-translations repo, the compiled .mo files were removed from version control. Because the tests workflow in this repository did not have the compile_catalog step (unlike our other workflows), the .mo files were entirely absent during tests.

Additional Information / CI Changes

  • Added setuptools to requirements-l10n.txt: Our translation compilation relies on setup.py, but starting in Python 3.12, setuptools is no longer bundled by default via ensurepip/venv. Adding it explicitly ensures the Python 3.12+ matrix builds succeed without throwing ModuleNotFoundError: No module named 'setuptools'.
  • Compile Catalog Step: Updated tests.yml to explicitly install l10n/requirements-l10n.txt and run python setup.py compile_catalog right before executing the tests to generate the missing .mo files.
  • Editable Install Mode: Changed the installation command to pip install -e . (editable mode). This ensures that the newly compiled .mo files generated directly inside the src directory are immediately available and resolvable by pytest.

All these changes make the tests workflow in this repo similar to the translations repo's workflow.


This pull request is categorized as a:

  • Other

Checklist

I ran pytest locally

  • All tests passed before submitting the PR

I included screenshots of any new or modified screens

  • N/A

I added or updated tests

  • N/A

I tested this PR hands-on on the following platform(s):


I have reviewed these notes:

  • Keep your changes limited in scope.
  • If you uncover other issues or improvements along the way, ideally submit those as a separate PR.
  • The more complicated the PR, the harder it is to review, test, and merge.
  • We appreciate your efforts, but we're a small team of volunteers so PR review can be a very slow process.
  • Please only "@" mention a contributor if their input is truly needed to enable further progress.
  • I understand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 0.8.7 Needs Code Review

Development

Successfully merging this pull request may close these issues.

1 participant