인기: 데이터 업데이트: 2026년 11월 17일

카테고리

인터넷1,416
커뮤니케이션328
오디오 및 비디오938
그래픽 및 디자인562
오피스 및 생산성1,180
개발 도구3,283
AI 도구607
보안 및 개인정보407
시스템 도구3,188
게임543
교육 및 과학242
네트워크 및 IT292

Rig 1.28.0 다운로드

Convention-first dev launcher across .NET, Node, Go, and Rust

현재 최신 버전입니다. · 출시일:

설치 파일 1.28.0

아키텍처형식설치 범위파일 크기다운로드SHA256
64비트 ZIP → 포터블 — — github.com VirusTotal
ARM64 ZIP → 포터블 — — github.com VirusTotal

링크와 SHA256은 Windows 패키지 관리자 커뮤니티 매니페스트에서 가져왔습니다. 실행하기 전에 다운로드한 파일의 해시를 비교해 보십시오.

릴리스 노트

🚀 Enhancements
- shiprig: shiprig can sign and notarize a velopack macOS app from secrets alone, with nothing in the login keychain. Put the Developer ID .p12 (base64) and its password in the velopack signing env as MACOS_SIGN_P12 and MACOS_SIGN_PASSWORD, and optionally an App Store Connect API key as MACOS_NOTARY_KEY (the .p8 as PEM text or base64), MACOS_NOTARY_KEY_ID and MACOS_NOTARY_ISSUER_ID. Each can be a doppler: reference. A signed macOS build then creates a throwaway keychain, imports the cert, stores the notary key under macos.notaryProfile, points vpk pack --keychain and the DMG's codesign/notarytool at it, and deletes it when the build ends, whether it succeeded, failed or was interrupted with Ctrl-C; a keychain left by a build that was killed outright is removed by the next signed build. A cert that doesn't hold macos.signIdentity, a notary key without a cert, notaryProfile or key id, or a cert with notaryProfile but no notary key, fails before anything is built. Errors from these steps never show the passwords. Builds without these variables behave as before.
- shiprig: shiprig's velopack packaging takes a macos.entitlements setting: a repo-root-relative .entitlements plist the macOS app is signed with, passed to vpk pack as --signEntitlements. Without it vpk signs with its bundled default, which grants JIT, unsigned executable memory, Apple Events automation, DYLD environment variables and disabled library validation. Like notaryProfile, it needs macos.signIdentity (a config with entitlements and no identity is rejected rather than shipping without them) and is skipped on a snapshot build. A path that doesn't exist fails the build before any channel is built.
🩹 Fixes
- shiprig: shiprig titles each per-package forge release after its tag again, as changesets' own action does: a single-package repo's release on v1.2.3 is titled v1.2.3 rather than <package>@1.2.3, a monorepo's @scope/pkg@1.2.3 keeps that title, and a tagTemplate or Go dir/v1.2.3 tag is the title as it renders. This restores the tag-named titles single-package repos had before shiprig-action moved onto shiprig forge-release. It applies to the release step and shiprig forge-release on GitHub, GitLab and Gitea, and forge-release --json reports that title as name. Combined releases are unchanged and still take their title from forgeRelease.name.

https://github.com/rigsmith/rigsmith/releases/tag/v1.28.0

프로그래밍 언어 및 SDK 인기 1위

전체 보기
  1. Go Programming Language프로그래밍 언어 및 SDK
  2. LLVM프로그래밍 언어 및 SDK · LLVM
  3. Deno프로그래밍 언어 및 SDK · Deno Land Inc.
  4. CMake프로그래밍 언어 및 SDK · Kitware
  5. Yarn프로그래밍 언어 및 SDK · Yarn Contributors
  6. pnpm프로그래밍 언어 및 SDK · pnpm
  7. Ccache프로그래밍 언어 및 SDK · Joel Rosdahl
  8. sbt프로그래밍 언어 및 SDK · Lightbend, Inc.
  9. BOINC프로그래밍 언어 및 SDK · Space Sciences Laboratory, U.C. Berkeley
  10. Dart SDK프로그래밍 언어 및 SDK · Google

RigSmith의 다른 프로그램

전체 보기
  • ChangeRig프로그래밍 언어 및 SDK · RigSmith
  • ShipRig프로그래밍 언어 및 SDK · RigSmith
  • ClaudeRig프로그래밍 언어 및 SDK · RigSmith
  • RigSmith프로그래밍 언어 및 SDK · RigSmith
  • claudeRig UIAI 어시스턴트 및 LLM · RigSmith
  • CodexRig클라우드 저장소 및 동기화 · RigSmith

태그

공유