Semantic Release Not Handling Package.json Or Files One Level Up Correctly

Current behavior

When using the following configuration, the @semantic-release/git plugin appears to push the changelog and any files located in the same or subdirectory of the releasing library to the target branch. However, it does not push the package.json files or any other files that are one level up (../) from the released library.

const commitUpdatedAssets = [
  '@semantic-release/git',
  {
   // Notice we use a regex and relative path and both fail but CHANGELOG.md works
    assets: ['../**/*/package.json', `${disRoot}/package.json`, `../beam/package.json`  'CHANGELOG.md'],
    message:
      'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}',
  },
];

const plugIns = [
  commitAnalyzer,
  releaseNotesGenerator,
  updatePackagesThatDepOnMeVersion,
  changelog,
  npm,
  github,
  commitUpdatedAssets,
];

Expected behavior

The @semantic-release/git plugin should respect other package.json files or files that are not in the released library and are one level up (../). These files should be pushed to the repository along with the files that are local to the library (./).

Start by reproducing the reported @semantic-release/git configuration with CHANGELOG.md, local package.json, and package.json paths using ../. Inspect the plugin's asset path handling and verify that files one level above the releasing library are included in the release commit, while existing local assets continue to work.