Skip to content

Update uap-core - #105

Open
tincho4t wants to merge 1 commit into
ua-parser:masterfrom
tincho4t:update-uap-core-oneplus-fix
Open

tincho4t wants to merge 1 commit into
ua-parser:masterfrom
tincho4t:update-uap-core-oneplus-fix

Conversation

@tincho4t

Copy link
Copy Markdown

Regenerates the embedded regex definitions with build.sh, moving the uap-core submodule from c941f1d (2024-09-27) to e3c5e63 (2026-08-11) — 99 upstream commits.

Motivation: this picks up the OnePlus device detection fix from ua-parser/uap-core#668. User agents with an empty build token (trailing ; )), e.g.

Mozilla/5.0 (Linux; Android 10; ONEPLUS A7010; ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.185 Mobile Safari/537.36

were falling through to Generic Smartphone instead of resolving to OnePlus. The regex data in this repo predates that fix, so Go consumers don't get it yet.

The sync also brings in roughly two years of other uap-core additions (new browser and device tokens — Microsoft Teams embedded browser, Ladybird, Steam embedded browsers, QtWebEngine, and many more).

Verification:

  • go test ./... in uaparser passes.
  • Parsing the UA above with the regenerated definitions returns family OnePlus ONEPLUS A7010, brand OnePlus, model ONEPLUS A7010; MODEL Build/... and clean MODEL) forms are unchanged.

🤖 Generated with Claude Code

Regenerate the embedded regex definitions via build.sh, moving the
uap-core submodule from c941f1d (2024-09-27) to e3c5e63 (2026-08-11).

Includes the OnePlus device detection fix from uap-core#668: user agents
with an empty build token (trailing '; )') were falling through to
Generic Smartphone.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@dgoldstein0

Copy link
Copy Markdown
Contributor

apologies for taking so long to get around to this, been a busy past few weeks... this looks fine to me but apparently I can't trigger CI on it anymore because I waited too long to take a look... 🤦 guess I'm going to have to add an empty commit before I can do that

@dgoldstein0

Copy link
Copy Markdown
Contributor

... which I probably can't do as the branch for this PR comes from your repo. can you add an empty commit so I can trigger the tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants