Create the ARIA live regions when the DOM is ready.

Git ignore the VSCode config dir

…implementation-common-example

Merge the example apps, only have one implementation for iOS and Android

No quotes for URLs

Update master branch from original repo.

Merge master from gutenberg

# This is the 1st commit message:

Publish the built plugin zip.

This adds a job to the Build Gutenberg Plugin Zip workflow that publishes the built zip to the GitHub Container Registry.

# This is the commit message #2:

`always()` check is necessary.

# This is the commit message #3:

Don't use arrays for `include` combinations.

# This is the commit message #4:

Adjust job names so it's clear what's being done.

This ensures the "Build Release Artifact" name is preserved when the assets are built for the Gutenberg plugin because that is a check that is required to be passing before a merge is allowed.

# This is the commit message #5:

Correct typo in environment variable.

# This is the commit message #6:

One more typo fix.

# This is the 1st commit message:

Change the package name to be more specific.

# This is the commit message #2:

Change the package name on GHCR.

Even though it's nested under the `gutenberg` repository, `wordpress-develop-build` could be confusing.

# This is the commit message #3:

Correct other relevant conditionals.

# This is the commit message #4:

Workflow file can be simplified now.

With better type casting to avoid truthy false values, the workflow can be less cautious.

# This is the commit message #5:

Fix one missed conditional.

* Publish the built plugin zip.

This adds a job to the Build Gutenberg Plugin Zip workflow that publishes the built zip to the GitHub Container Registry.

* `always()` check is necessary.

* Do not attempt to publish to GHCR in forks.

* Hardcode the org/repository.

The organization and repository names cannot have capital letters.

Since the conditionals ensure the job only runs in the WordPress/gutenberg repository, this value can be safely hard-coded.

* Prepare a plugin artifact for `wordpress-develop`

Because the `wp-build` package performs some substitutions, the script needs to be run with `IS_GUTENBERG_PLUGIN` set to `false` an `IS_WORDPRESS_CORE` set to `true`.

* # This is a combination of 6 commits.
# This is the 1st commit message:

Publish the built plugin zip.

This adds a job to the Build Gutenberg Plugin Zip workflow that publishes the built zip to the GitHub Container Registry.

# This is the commit message #2:

`always()` check is necessary.

# This is the commit message #3:

Don't use arrays for `include` combinations.

# This is the commit message #4:

Adjust job names so it's clear what's being done.

This ensures the "Build Release Artifact" name is preserved when the assets are built for the Gutenberg plugin because that is a check that is required to be passing before a merge is allowed.

# This is the commit message #5:

Correct typo in environment variable.

# This is the commit message #6:

One more typo fix.

* Publish the built plugin zip.

This adds a job to the Build Gutenberg Plugin Zip workflow that publishes the built zip to the GitHub Container Registry.

* # This is a combination of 5 commits.
# This is the 1st commit message:

Change the package name to be more specific.

# This is the commit message #2:

Change the package name on GHCR.

Even though it's nested under the `gutenberg` repository, `wordpress-develop-build` could be confusing.

# This is the commit message #3:

Correct other relevant conditionals.

# This is the commit message #4:

Workflow file can be simplified now.

With better type casting to avoid truthy false values, the workflow can be less cautious.

# This is the commit message #5:

Fix one missed conditional.

* Make the package name more specific.

Co-Authored-By: Dennis Snell <[email protected]>

* Allow plugin name to be overridden.

This allows the plugin name setting to be overridden more easily so that GitHub Actions can change the behavior of the build package.

* Allow plugin name to be overridden.

This allows the plugin name setting to be overridden more easily so that GitHub Actions can change the behavior of the build package.

* # This is a combination of 4 commits.
# This is the 1st commit message:

Allow plugin name to be overridden.

This allows the plugin name setting to be overridden more easily so that GitHub Actions can change the behavior of the build package.

# This is the commit message #2:

Support `wpPlugin.name` without env variables

# This is the commit message #3:

Ensure boolean casting is more reliable.

# This is the commit message #4:

Remove debug line.

* Allow plugin name to be overridden.

This allows the plugin name setting to be overridden more easily so that GitHub Actions can change the behavior of the build package.

* Make the default `base-url` value context aware.

* Allow relevant values to be overridden more easily

* Skip PHP transforms when building for WP Core.

* Document environment variable in README.

* Improve utility function name and inline docs.

* Update CHANGELOG.

* Account for more truthy values in `castBool`

* Remove unrelated change.

Co-Authored-By: Dennis Snell <[email protected]>

* Add a description to the ORAS step.

Co-Authored-By: Dennis Snell <[email protected]>

* Switch to using `.gz` over `.zip`.

Co-Authored-By: Dennis Snell <[email protected]>

Push some debug code.

Co-Authored-By: Dennis Snell <[email protected]>

Make corrections to new compression steps.

Change directory to compress.

Avoid `tar` writing to itself.

Unzip GitHub artifact.

Zip files are rezipped by upload-artifact.

Relax repo specific rules

Debugging.

Adjust.

More changes.

Remove debug code.

* Improvements to the boolean casting function.

Co-Authored-By: Dennis Snell <[email protected]>

* Final coding standards fixes.

* Remove stray unnecessary `eslint-enable`.

* Remove the `WP_PLUGIN_NAME` env variable.

This eliminates an environment variable that's essentially only present to facilitate builds for `wordpress-develop`.

---------

Co-authored-by: desrosj <[email protected]>
Co-authored-by: dmsnell <[email protected]>
Co-authored-by: youknowriad <[email protected]>