Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: m43nu/base-stack
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: forge-42/base-stack
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 7 commits
  • 19 files changed
  • 1 contributor

Commits on Jul 18, 2025

  1. update deps (forge-42#53)

    Fixes #
    
    # Description
    
    Please include a summary of the change and which issue is fixed. Please
    also include relevant motivation and context.
    List any dependencies that are required for this change.
    
    ## Type of change
    
    Please mark relevant options with an `x` in the brackets.
    
    - [ ] Bug fix (non-breaking change which fixes an issue)
    - [ ] New feature (non-breaking change which adds functionality)
    - [ ] Breaking change (fix or feature that would cause existing
    functionality to not work as expected)
    - [ ] This change requires a documentation update
    - [ ] Algorithm update - updates algorithm
    documentation/questions/answers etc.
    - [ ] Other (please describe):
    
    # How Has This Been Tested?
    
    Please describe the tests that you ran to verify your changes. Provide
    instructions so we can reproduce. Please also
    list any relevant details for your test configuration
    
    - [ ] Integration tests
    - [ ] Unit tests
    - [ ] Manual tests
    - [ ] No tests required
    
    # Reviewer checklist
    
    Mark everything that needs to be checked before merging the PR.
    
    - [ ] Check if the UI is working as expected and is satisfactory
    - [ ] Check if the code is well documented
    - [ ] Check if the behavior is what is expected
    - [ ] Check if the code is well tested
    - [ ] Check if the code is readable and well formatted
    - [ ] Additional checks (document below if any)
    
    # Screenshots (if appropriate):
    
    # Questions (if appropriate):
    AlemTuzlak authored Jul 18, 2025
    Configuration menu
    Copy the full SHA
    982db97 View commit details
    Browse the repository at this point in the history

Commits on Sep 17, 2025

  1. version bump

    AlemTuzlak committed Sep 17, 2025
    Configuration menu
    Copy the full SHA
    30357cd View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    add2cf8 View commit details
    Browse the repository at this point in the history

Commits on Oct 8, 2025

  1. update deps to latest versions (forge-42#56)

    # Description
    
    Update deps to latest versions
    AlemTuzlak authored Oct 8, 2025
    Configuration menu
    Copy the full SHA
    99243e2 View commit details
    Browse the repository at this point in the history

Commits on Oct 9, 2025

  1. upgrade react-compiler to v1 (forge-42#57)

    Upgrade react-compiler to v1
    AlemTuzlak authored Oct 9, 2025
    Configuration menu
    Copy the full SHA
    8d7367f View commit details
    Browse the repository at this point in the history

Commits on Oct 14, 2025

  1. update deps

    AlemTuzlak committed Oct 14, 2025
    Configuration menu
    Copy the full SHA
    d791d9e View commit details
    Browse the repository at this point in the history

Commits on Dec 25, 2025

  1. Feat/update deps (forge-42#58)

    Fixes #
    
    # Description
    
    Please include a summary of the change and which issue is fixed. Please
    also include relevant motivation and context.
    List any dependencies that are required for this change.
    
    ## Type of change
    
    Please mark relevant options with an `x` in the brackets.
    
    - [ ] Bug fix (non-breaking change which fixes an issue)
    - [ ] New feature (non-breaking change which adds functionality)
    - [ ] Breaking change (fix or feature that would cause existing
    functionality to not work as expected)
    - [ ] This change requires a documentation update
    - [ ] Algorithm update - updates algorithm
    documentation/questions/answers etc.
    - [ ] Other (please describe):
    
    # How Has This Been Tested?
    
    Please describe the tests that you ran to verify your changes. Provide
    instructions so we can reproduce. Please also
    list any relevant details for your test configuration
    
    - [ ] Integration tests
    - [ ] Unit tests
    - [ ] Manual tests
    - [ ] No tests required
    
    # Reviewer checklist
    
    Mark everything that needs to be checked before merging the PR.
    
    - [ ] Check if the UI is working as expected and is satisfactory
    - [ ] Check if the code is well documented
    - [ ] Check if the behavior is what is expected
    - [ ] Check if the code is well tested
    - [ ] Check if the code is readable and well formatted
    - [ ] Additional checks (document below if any)
    
    # Screenshots (if appropriate):
    
    # Questions (if appropriate):
    AlemTuzlak authored Dec 25, 2025
    Configuration menu
    Copy the full SHA
    5539524 View commit details
    Browse the repository at this point in the history
Loading