Skip to content

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

gear-tech / gear Public

Notifications You must be signed in to change notification settings
Fork 106
Star 241

Code
Issues 234
Pull requests 25
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

PR

feat(wasm-builder): switch to new `wasm32v1-none` target #5155

Sign in to view logs

Sign in to view logs

feat(wasm-builder): switch to new `wasm32v1-none` target

feat(wasm-builder): switch to new `wasm32v1-none` target #5155

Summary
Jobs
- status
- docs
- linux
  
  fuzzer
- dynamic-profiles
  
  linux (debug)
  
  win-cross (debug)
  
  win-native
  
  macos
- validator
- check-node-sync
Run details
- Usage
- Workflow file

Usage Workflow file

status

succeeded Feb 3, 2025 in 10s

Loading

Re-running jobs...

You can’t perform that action at this time.

feat(wasm-builder): switch to new wasm32v1-none target #5155

status

status

Re-running jobs...

feat(wasm-builder): switch to new `wasm32v1-none` target #5155