The `GITHUB_REF_NAME` variable only works for tags pushed by developers.
When calling the docker.yml workflow from tag-release.yml, the contents
of `GITHUB_REF_NAME` is `main`, the branch that the GitHub Action is
running on. This will fix the version output for x.y.0 tags created by
tag-release.yml.
Because:
* We want to include more information in the recovery key file, and rendering for localized content in .txt format was inconsistent accross apps and platforms.
This commit:
* Add react-pdf library and associated dependencies for client-side PDF generation
* Add DownloadRecoveryKeyPDF component to handle PDF generation and download
* Create RecoveryKeyPDF with styling and l10n
* Update tests for recovery key
* Add pdf-parse library to test PDF content with Playwright
* Add font assets to fxa-settings for PDF creation
* Remove fonts from CDN assets folder (no longer needed)
* Use mono font for account recovery key in React app and PDF to help user differentiate between similar characters such as O and 0
Closes #FXA-7223
Because:
* Fonts need to be available from CDN for client-side PDF generation
This commit:
* Adds font files to support basic font weights for fxa's supported languages
* Add font files to asset upload script
* Add documentation about font files
Issue #FXA-7223
Because:
* Our string extraction CI job is failing when changes are found and l10n-devs has not been requested for review yet
This commit:
* Captures grep exit code to compare against directly, as grep -q "fxa-l10n" was failing and breaking out of the command pipeline with exit code 1
Because:
* This directory is not always present. When we try to just 'rm' when it doesn't exist, a hidden error is thrown
This commit:
* Simply adds "-rf" to the rm command for ./locale/templates/LC_MESSAGES/*
Fixes 7862
Because:
- We are cleaning up npm scripts in preparation for nx
This Commit:
- Replaces npm run with yarn
- Removes npm-run-all package
- Replaces npm install -g with yarn global add
- Updates references to npm install or npm run in readme files
Because:
* We could encourage more consistent builds by using an environment
built in an action instead of on developer machines
This commit:
* Creates a github action
Because:
- we want to use the latest node LTS major version
This commit:
- upgrades FxA to use node 18, with two workarounds
- Webpack uses a hash algorithm that's no longer supported by default
in node 17+, causing build failures; --openssl-legacy-provider is
used as the workaround
- dns.lookup in node 17+ by default returns the results in the same
order as they are from the resolver, which could lead to
'localhost' resolving to ::1; --dns-result-order=ipv4first is used
as the workaround
Because:
- We want to avoid redundant git clone operations
- We want to reduce the number of ftl bundles requested on the client side.
This Commit:
- Adds _scripts/l10n/*.sh for conducting l10n build operations
- Bundles ftl files together into ftl main
- Removes bundle prop on AppLocalizer, so that it uses the default, [main.ftl]
- Replace - with _ in locale names when resolving ftl files
- Removes clone-l10n.sh
Because:
* L10n workflow to flag l10n reviewers to gettext changes fails silently because npx grunt script doesn't overwrite previously extracted files.
This commit:
* Removes files from target folder to ensure all changes in files are present.
Because:
- We need to pull the latest pdfs from legal-docs into the fxa
assets folder.
This commit:
- Create a script to copy the latest pdfs into assets/legal.
- Create a Github Action to automatically pull in the pdfs from
legal-docs, and open a pull request to move pdfs into assets/legal.
Closes #fxa-5100
Because:
* Action fails under certain conditions when it tries to checkout the base SHA but it cannot be found
This commit:
* Adds an explicit fetch for the base SHA to ensure it can be checked out
Because:
* Certain modern javascript syntax breaks the l10n-extract process.
* Gettext strings currently are not reviewed for localization issues until export to Pontoon
This commit:
* Runs "npx grunt l10n-extract" whenever a PR makes a change to fxa-content-server. An unsupported syntax will cause the build to fail, alerting ahead of time.
* Flags mozilla/fxa-l10n for review if a change creates new gettext strings