chore(main): release web3telegram 0.1.0-alpha.10

[iexec-release-please-app]

🤖 I have created a release beep boop

0.1.0-alpha.10 (2026-02-16)

Changed

• stop enforcing SCONE as unique TEE framework for orders (#97) (6864435)

---

This PR was generated with Release Please. See documentation.

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on March 10.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint@​8.57.1 ⏵ 8.51.0	-7
	node-forge@​1.3.1
	jest@​29.7.0
	@​typescript-eslint/​parser@​6.21.0 ⏵ 6.7.5
	eslint-config-prettier@​9.1.2 ⏵ 9.0.0
	@​iexec/​dataprotector-deserializer@​0.1.1
	joi@​17.11.0
	@​typescript-eslint/​eslint-plugin@​6.21.0 ⏵ 6.7.5			+1
	jszip@​3.10.1
	iexec@​8.22.0
	eslint-plugin-import@​2.32.0 ⏵ 2.28.1	+1
	node-fetch@​2.7.0
	prettier@​2.8.8
	dotenv@​10.0.0 ⏵ 16.3.1			+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: TimelockController vulnerability in OpenZeppelin Contracts in npm @openzeppelin/contracts CVE: GHSA-fg47-3c2x-m2wr TimelockController vulnerability in OpenZeppelin Contracts (CRITICAL) Affected versions: >= 4.0.0 < 4.3.1; >= 3.3.0 < 3.4.2 Patched version: 3.4.2 From: dapp/package-lock.json → npm/iexec@8.22.0 → npm/@openzeppelin/contracts@3.3.0 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openzeppelin/contracts@3.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		GitHub dependency: npm @ensdomains/ens-contracts depends on Arachnid/clones-with-immutable-args Dependency: clones-with-immutable-args@Arachnid/clones-with-immutable-args@#featur Location: Package overview From: dapp/package-lock.json → npm/iexec@8.22.0 → npm/@ensdomains/ens-contracts@1.6.0 ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Publish the GitHub dependency to a public or private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@ensdomains/ens-contracts@1.6.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm registry-auth-token is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: dapp/package-lock.json → npm/iexec@8.22.0 → npm/registry-auth-token@3.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/registry-auth-token@3.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[iexec-release-please-app]

🤖 Created releases:

• web3telegram-v0.1.0-alpha.10

🌻