Repository navigation
Release v0.4.3 - #181
Merged
Merged
Release v0.4.3#181
Conversation
An opt-in wrapper class for block buttons on sign-in pages: white with a gray-300 border in light mode, gray-900 with a gray-700 border in dark, and a hover that shifts the background and strengthens the border. It gives the console's provider buttons and the extension buttons below them (Customer Portal, Track Order) one shared look. Colours are custom properties on the wrapper, so a caller can re-colour a single button and keep the same border, hover and transition.
feat(button): add btn-auth, a neutral sign-in page button style
A "Continue with <provider>" button for sign-in and sign-up pages: a btn-auth block button with the provider's logo in the icon slot at the far left, re-coloured where a provider's guidelines call for it. Google and Microsoft stay on btn-auth's white with their full-colour logos. Apple is black and GitHub near-black. Every provider is gray-900 in dark mode, where Google's G sits on the white disc Google requires. Moved here from the console so the Fleetbase Cloud sign-up page, which is an engine component and can't use console components, can render the same buttons. RELEASE.md adds it to v0.4.3.
feat(oauth): add OauthProviderButton and OauthProviderLogo
Typed non-digits are cancelled at beforeinput, and pasted or autofilled text is stripped to digits, a leading plus and formatting separators before intl-tel-input formats it. Fixes fleetbase/fleetbase#403.
This was referenced Sep 22, 2026
Keep letters out of the phone input
…icker The picker loaded CARTO's basemaps.cartocdn.com tiles for light and dark_all, and Stadia Maps' alidade_smooth_dark for dark. CARTO now requires an API key and shows an "API key required" watermark without one, and Stadia needs a key outside localhost. Every theme now uses the keyless OpenStreetMap tile server, the same default as Fleet-Ops, with OpenStreetMap's attribution on the tile layer as its usage policy requires. OpenStreetMap has no dark style, so the dark themes use the same tiles. A custom https:// URL is still passed through unchanged. DEFAULT_TILE_URL and DEFAULT_TILE_ATTRIBUTION are exported, and a test covers every theme keyword and a custom URL.
CI triggered on push to main, release/v* and dev-v*, and on pull_request into the same branches. A release branch always has a pull request, so every push to it ran the whole suite twice. Pushes now trigger it only on main and tags (tags still publish); pull requests still cover release and dev branches. A concurrency group cancels a superseded run on the same pull request or branch. Each tag is its own ref, so a publish is never cancelled.
Since 074db0c, CI's test step never exited: all tests passed, then the run waited until cancelled. That commit's integration test imported components/coordinates-input at the top of the file. The component imports @fleetbase/ember-core/utils/get-with-default, which the dummy app doesn't provide, so loading that test file failed. CI filters integration tests out but still loads every test file, and the run never recovered from the failed load. - The tile choice moves out of the component into utils/leaflet-tile-source, which has no ember-core dependency. The component uses it, with unchanged behaviour. - A unit test covers it, and runs in CI (integration tests don't): every keyword gives OpenStreetMap, an https:// URL is kept, and OpenStreetMap's attribution is present. - The integration test goes back to what it was before 074db0c. - The test job gets a 20-minute timeout (the suite takes about 3), so a future hang fails fast instead of running until someone cancels it. Verified locally with CI's own command (ember test --filter='!Integration'): 78/78 pass and the run exits. Before this change it hung after test 75.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release branch for v0.4.3.
This branch collects:
btn-auth, a neutral button style for sign-in pages. It's shared by the console's "Continue with ..." provider buttons and the extension buttons below them: Customer Portal (style(login): use ember-ui's btn-auth for the Customer Portal button customer-portal#17) and Track Order (style(login): use ember-ui's btn-auth for the Track Order button fleetops#339).package.jsonis0.4.3, and the first line ofRELEASE.mdnames v0.4.3, sorelease.ymltags on merge.Merge #179 into this branch first.
The code coverage campaign that previously sat on
release/v0.4.3(#177) moved tofeature/code-coverage-campaign(#180). It isn't part of this release.