Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: added version 1.1.2 checksum to versions list for '@metamask/s… #735

Merged
merged 1 commit into from
Aug 13, 2024

Conversation

k-g-j
Copy link
Contributor

@k-g-j k-g-j commented Aug 12, 2024

Changes to add a new version of the SSK to the registry

@k-g-j k-g-j requested review from Montoya and a team as code owners August 12, 2024 22:01
Copy link
Contributor

@bowensanders bowensanders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked, LGTM ✅

@FrederikBolding FrederikBolding merged commit fb74090 into main Aug 13, 2024
16 checks passed
@FrederikBolding FrederikBolding deleted the chore/add-ssk-version-1.1.2 branch August 13, 2024 07:54
k-g-j added a commit to MetaMask/metamask-extension that referenced this pull request Aug 13, 2024
#26378)

## **Description**

Adds an e2e test where the account Snap suggests the same account name
more than once.
The expected behavior is that the default account names should have an
increasing numeric suffix, e.g.:

- SSK Account
- SSK Account 2
- SSK Account 3

Dependency: MetaMask/snaps-registry#735

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/26378?quickstart=1)

## **Related issues**

Fixes: https://github.com/MetaMask/accounts-planning/issues/548

## **Manual testing steps**

1. Install the [Snap Simple
Keyring](https://metamask.github.io/snap-simple-keyring/latest/) and
connect to the dapp
2. Create an account -> name of 1st account should be "SSK Account"
3. Create more accounts -> 2nd account should be "SSK Account 2" and so
forth
4. Try renaming a numbered SSK Account to a higher number, the next
account created should be the lowest possible available "SSK Account X"
with X being the lowest available number

## **Screenshots/Recordings**


https://github.com/user-attachments/assets/b2404a8f-dbe9-468f-9ca3-aac1e028acae

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
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.

3 participants