| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Recreated from #64
#64 includes non-linear commits that rebased from old version of main
branch which contains large files.
## Summary by Sourcery
Update project metadata and links for the new HydroRoll-Team repository
and bump versions for the alpha.1 pre-release.
New Features:
- Add changelog files for the Tauri app and UI packages documenting the
v0.2.0-alpha.1 release.
Enhancements:
- Bump Tauri and UI package versions from 0.2.0-alpha to 0.2.0-alpha.1
to reflect the new pre-release.
- Update repository URLs, API endpoints, and commit links to point to
the HydroRoll-Team/DropOut GitHub organization.
Documentation:
- Add release notes for v0.2.0-alpha.1 in separate changelog files for
the backend and UI.
|
| | |\
| |/
|/| |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Updated repository URL in Cargo.toml
- Updated GitHub API endpoint in main.rs
- Updated commit links in HomeView.svelte
- Updated issue template links in config.yml
Reviewed-by: Claude Sonnet 4.5
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Refer: http://semifold.noctisynth.org/
## Summary by Sourcery
Adopt Semifold-based release management and prepare the project for a
0.2.0-alpha pre-release across Rust and UI packages.
New Features:
- Introduce Semifold CI release workflow to orchestrate builds,
publishing, and changelog management.
- Add Semifold status workflow to report release status on pull
requests.
- Add workspace-level Node tooling and scripts to manage Tauri version
bumping and project preparation.
Enhancements:
- Refactor GitHub Actions workflows for build, test, check, and lint to
simplify pnpm usage, update action versions, and standardize artifact
paths.
- Move Rust profile configuration into a new Cargo workspace and add a
pnpm workspace for the UI package.
- Configure Semifold changelog and release metadata for Rust and Node
packages, including alpha pre-release tagging.
Build:
- Replace the tag-triggered GitHub release workflow with a branch-based
Semifold CI pipeline that builds artifacts for Linux, macOS, and Windows
and uploads them for publishing.
- Update CI action versions (checkout, setup-node, upload-artifact,
download-artifact) and adjust Rust cache configuration and artifact
locations.
- Add root workspace package.json, pnpm-workspace.yaml, and pnpm
overrides to centralize tooling and dependency management.
CI:
- Add a dedicated Semifold status GitHub Actions workflow for pull
requests to main.
- Update existing check, lint, test, and build workflows to align with
the new workspace layout and artifact directories.
Deployment:
- Integrate Semifold configuration for automated publishing to crates.io
and npm, including pre-checks, post-version hooks, and use of stored
build artifacts in releases.
Tests:
- Adjust test workflow artifact paths to match the new target directory
structure and workspace configuration.
Chores:
- Remove unused Python packaging files and old Node lockfiles that are
no longer part of the build or release process.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Create InstanceEditorModal.svelte with 4 tabs:
* Info: Instance name, notes, metadata (created date, last played)
* Version: Mod loader switcher and version display
* Files: File browser for mods/resourcepacks/shaderpacks/saves/screenshots
* Settings: Memory override and JVM arguments customization
- Wire InstanceEditorModal to InstancesView with Edit button
- Add FileInfo type definition to types/index.ts
- Fix accessibility issues: proper button roles, keyboard events
- All TypeScript and Svelte compilation errors resolved
- Enable comprehensive per-instance configuration management
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Create multi-step InstanceCreationModal with version and mod loader selection
- Step 1: Instance name input
- Step 2: Minecraft version selection with search and filtering
- Step 3: Mod loader choice (vanilla/Fabric/Forge) with version selection
- Automatically installs vanilla version + mod loader during creation
- Wire new modal to InstancesView, replace old simple creation dialog
- Remove unused confirmCreate function
This wizard integrates version management into instance creation workflow,
streamlining the user experience by combining instance setup and version
installation into a single guided process.
|
| | |
| |
| |
| |
| |
| |
| | |
- Sync instance.version_id after start_game, install_fabric, install_forge
- Add jvm_args_override and memory_override to Instance struct
- Add file management commands: list_instance_directory, delete_instance_file, open_file_explorer
- Support per-instance settings overrides (Java args, memory)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Add migrate_to_shared_caches() with hard link preference
- SHA1-based deduplication across all instances
- Copy fallback for cross-filesystem scenarios
- Auto-enable use_shared_caches after successful migration
- UI shows statistics: moved files, hardlinks/copies, MB saved
|
| | |
| |
| |
| |
| |
| | |
- Add pass_filenames: false to fmt hook
- Add -- separator for cargo fmt args
- Manually format code with cargo fmt
|
| | | |
|
| | |
| |
| |
| | |
constructor
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
## Overview
Fixed critical multi-instance isolation bugs where versions, mod loaders, and
instance state were not properly isolated between instances. These changes ensure
full data isolation and consistent instance metadata.
## Bug Fixes - P0 (Critical Isolation Issues)
### 1. Backend: get_versions() command isolation
- Problem: Used global app_data_dir instead of instance-specific game_dir
- Fix: Added instance_id parameter, now queries instance.game_dir
- Impact: Versions are now properly isolated per instance
### 2. Frontend: delete_version missing instanceId
- Problem: Frontend passed only versionId, not instanceId
- Fix: Updated VersionsView.svelte to pass instanceId parameter
- Impact: Version deletion now targets correct instance
### 3. Frontend: get_version_metadata missing instanceId
- Problem: Metadata queries didn't specify which instance to check
- Fix: Updated VersionsView.svelte to pass instanceId parameter
- Impact: Version info displayed per-instance correctly
### 4. Frontend: Instance switching doesn't refresh versions
- Problem: Switching instances didn't reload version list
- Fix: Added $effect hook in GameState to watch activeInstanceId changes
- Impact: Version list auto-refreshes on instance switch
## Bug Fixes - P1 (State Synchronization)
### 5. Backend: install_fabric doesn't update Instance.mod_loader
- Problem: Instance.mod_loader field wasn't updated after installation
- Fix: Added instance_state.update_instance() call
- Impact: Instance metadata stays in sync
### 6. Backend: install_forge doesn't update Instance.mod_loader
- Problem: Instance.mod_loader field wasn't updated after installation
- Fix: Added instance_state.update_instance() call
- Impact: Instance metadata stays in sync
### 7. Backend: delete_version doesn't clean up Instance state
- Problem: Deleting version didn't clear Instance.version_id or .mod_loader
- Fix: Added cleanup logic to clear stale references
- Impact: Instance state remains valid after deletion
## Testing
- Added comprehensive integration tests in instance_isolation_tests.rs
- Tests document 10 key scenarios for multi-instance isolation
- All code compiles cleanly with no errors
|
| |\ \ |
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \ |
|
| | | |\ \
| |_|/ /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update parse_java_version() to properly handle:
- Build metadata (strip '+' and everything after)
- Trailing garbage (strip '-' and everything after, e.g. -Ubuntu)
- Underscore version separators (1.8.0_411 -> 1.8.0.411)
This ensures Java versions are correctly parsed on all platforms:
- Old format: 1.8.0_411 (Java 8 update 411)
- New format: 21.0.3+13-Ubuntu (Java 21 with build metadata)
- Short format: 17.0.1 (Java 17 update 1).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add find_root_version() function to walk the inheritance chain and find
the root vanilla Minecraft version from a modded version (Fabric/Forge).
This is useful for determining which vanilla version's client.jar should
be used when launching modded versions, as modded versions inherit from
vanilla versions but don't contain their own client.jar.
The function follows the inheritsFrom field recursively until reaching
a version without a parent (the root vanilla version).
|