Change generate-license-file version to match that of other search sdks
#231
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not sure why this file has new changes from this PR (#229), but this is blocking new releases. Therefore, I reran `npm run build`.
anguyen-yext2
changed the title
generate-license-file version to match that of other search sdks
mkouzel-yext
approved these changes
Oct 20, 2025
anguyen-yext2
added a commit
that referenced
this pull request
Oct 22, 2025
* Version 2.5.3 ### Changes - Adds OpenAt matcher - removes a test vulnerability * Add name property for near field value filters (#225) Bumps search-headless version to include change that added optional name property for near field value filters. * Automated update to THIRD-PARTY-NOTICES from github action's 3rd party notices check --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * Support trusted publishing with OIDC (#227) J=WAT-5079 TEST=manual * Bump search-headless version (to be published as v2.6.0) (#229) which includes change that supports facetAllowlist query parameter for vertical searches --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * Change `generate-license-file` version to match that of other search sdks (#231) This was causing different THIRD-PARTY-NOTICES files generated via npm run generate-notices vs our github action. --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * release: v2.6.0-beta.0 * release: v2.6.0 --------- Co-authored-by: Fondryext <160865254+Fondryext@users.noreply.github.com> Co-authored-by: mkouzel-yext <mkouzel@yext.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: anguyen-yext2 <143001514+anguyen-yext2@users.noreply.github.com> Co-authored-by: anguyen-yext2 <anguyen@yext.com>
anguyen-yext2
added a commit
that referenced
this pull request
Nov 6, 2025
* Version 2.5.3 ### Changes - Adds OpenAt matcher - removes a test vulnerability * Add name property for near field value filters (#225) Bumps search-headless version to include change that added optional name property for near field value filters. * Automated update to THIRD-PARTY-NOTICES from github action's 3rd party notices check --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * Support trusted publishing with OIDC (#227) J=WAT-5079 TEST=manual * Bump search-headless version (to be published as v2.6.0) (#229) which includes change that supports facetAllowlist query parameter for vertical searches --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * Change `generate-license-file` version to match that of other search sdks (#231) This was causing different THIRD-PARTY-NOTICES files generated via npm run generate-notices vs our github action. --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> * release: v2.6.0-beta.0 * release: v2.6.0 * Removed `version_update` workflow (#235) Versioning will be handled by the `publish` workflow. Note: This PR does not need be published on its own. Once merged, future PR's won't trigger the `version_update` workflow anymore. --------- Co-authored-by: Fondryext <160865254+Fondryext@users.noreply.github.com> Co-authored-by: mkouzel-yext <mkouzel@yext.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: anguyen-yext2 <143001514+anguyen-yext2@users.noreply.github.com> Co-authored-by: anguyen-yext2 <anguyen@yext.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was causing different THIRD-PARTY-NOTICES files generated via
npm run generate-noticesvs our github action.