Skip to content

feat: rename internal type-js alias to organization #1410

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 3, 2025
Merged

feat: rename internal type-js alias to organization #1410

merged 1 commit into from
Jun 3, 2025

Conversation

tabaktoni
Copy link
Member

Motivation and Resolution

Prevent future attempts to create false packages by using organization-named aliases.

Checklist:

  • Performed a self-review of the code
  • Rebased to the last commit of the target branch (or merged it into my branch)
  • Linked the issues which this PR resolves
  • Documented the changes in code (API docs will be generated automatically)
  • Updated the tests
  • All tests are passing

@penovicp penovicp merged commit d19cb57 into develop Jun 3, 2025
2 of 3 checks passed
@penovicp penovicp deleted the secure-types-alias branch June 3, 2025 08:04
github-actions bot pushed a commit that referenced this pull request Jun 4, 2025
@semantic-release-bot
chore(release): 7.5.0 [skip ci]
723503d 
# [7.5.0](v7.4.0...v7.5.0) (2025-06-04)

### Bug Fixes

* snip29 - timeBounds seconds (number), public preparePaymasterTransaction  ([#1408](#1408)) ([8cd4fa8](8cd4fa8))

### Features

* rename internal types-js alias to include organization scope ([#1410](#1410)) ([d19cb57](d19cb57))
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 4, 2025

🎉 This PR is included in version 7.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

@penovicp penovicp penovicp approved these changes

Assignees
No one assigned
Labels
released on @next
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tabaktoni @penovicp