v1.0.0

@oroinc/piece-orocommerce 1.0.0

Built by the release workflow from the tagged commit, with every check CI runs on a pull request:
lint, the test suite, the translation check, the check that the fetched Activepieces tree is
unmodified, the checks on the packed artifact, and the metadata snapshot that holds the piece's
surface still across pin bumps.

Release identity

Tag	v1.0.0
Commit	9a09efa2db8a6fd8c53843a8924c653c687388d1
Activepieces pin (.ap-pin)	23e0c254979c73cfbfbde00242668ee873e79508
Artifact	oroinc-piece-orocommerce-1.0.0.tgz
sha256 of the artifact	64faf5b2380d60743fe74f10d2bbd63af9a35619a61f7f93a1e7fc560da738d0
sha256 of package/src/index.js inside it	10c9c26f7110fc56be41a6bcf99ac1163bd77b4fde63581ed81f454485268359

The piece ships as one bundled file with no install step, and the Activepieces framework and common
package are inlined into it from the pinned commit. Check a download against the tarball hash. The
hash of package/src/index.js identifies the code that actually runs, and stays true when the
artifact is repackaged, as it is when npm serves a published version. Either way:

shasum -a 256 oroinc-piece-orocommerce-1.0.0.tgz
tar -xzOf oroinc-piece-orocommerce-1.0.0.tgz package/src/index.js | shasum -a 256

The build is reproducible: the same commit and the same pin pack a byte-identical tarball on
another machine. That is worth knowing but is not a substitute for the hashes above, because it only
holds while both stay where they are.

This version is never rebuilt or republished. Anything that needs fixing ships as a new version.