Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
c73c6ba
feat(github): add issue and PR templates
ErenayDev Nov 21, 2025
9854bf0
refactor(workspace): migrate to multi-crate workspace structure
ErenayDev Feb 23, 2026
168c9c1
refactor(core): remove old monolithic source structure
ErenayDev Feb 23, 2026
36fcf79
chore(tooling): remove cargo-bin wrapper and custom aliases
ErenayDev Feb 23, 2026
7f97551
chore: remove root-level test artifacts
ErenayDev Feb 23, 2026
36885b7
chore(github): update PR template location
ErenayDev Feb 23, 2026
88f75c6
chore(config): add node_modules to gitignore
ErenayDev Feb 23, 2026
bccbdae
feat(runtime): add shared memory IPC runtime and examples
ErenayDev Feb 24, 2026
c921791
chore(pre-commit): disable end-of-file-fixer hook
ErenayDev Feb 24, 2026
281f672
ci: switch runners from ubuntu-latest to self-hosted
ErenayDev Feb 27, 2026
5aca737
build: bump workspace to v0.1.3, update swc_core and throbber-widgets…
ErenayDev Feb 27, 2026
8ac04c5
refactor: replace strip_type with typescript transform using GLOBALS …
ErenayDev Feb 27, 2026
6c24a7d
docs: rewrite README with simplified structure and sponsor section
ErenayDev Feb 27, 2026
e99e8bb
chore: add .checkpoint to gitignore
ErenayDev Feb 27, 2026
d47eeb2
chore: add oranda output to gitignore
ErenayDev Feb 27, 2026
4b5e4a1
docs: add installation and release documentation
ErenayDev Feb 27, 2026
a4033e3
ci: add release and web workflows
ErenayDev Feb 27, 2026
4693a74
docs: add crate-level READMEs
ErenayDev Feb 27, 2026
89a2f6f
chore: add project metadata and distribution config
ErenayDev Feb 27, 2026
ecc723b
chore: remove tracked .checkpoint artifacts
ErenayDev Feb 27, 2026
710bc85
docs: update CHANGELOG for v0.1.3
ErenayDev Feb 27, 2026
9afc210
build: allow dirty ci config for cargo-dist
ErenayDev Feb 27, 2026
efe4094
Merge branch 'main' into develop
ErenayDev Feb 27, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
File renamed without changes.
3 changes: 0 additions & 3 deletions .cargo/config.toml

This file was deleted.

16 changes: 16 additions & 0 deletions .github/DISCUSSION_TEMPLATE/ideas.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
title: "[Idea] "
labels: discussion
---

## Summary
Briefly describe your idea.

## Problem
What problem does this solve?

## Proposed Solution
What’s your suggested approach?

## Benefits
Why should this be considered?
31 changes: 0 additions & 31 deletions .github/ISSUE_TEMPLATE/bug_report.md

This file was deleted.

98 changes: 98 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
name: Bug Report
description: Report a bug in the system
title: "[Bug]: "
labels: ["bug"]
assignees:
- ErenayDev
body:
- type: markdown
attributes:
value: |
Please provide detailed information about the bug to help us resolve it quickly.

- type: textarea
id: description
attributes:
label: Bug Description
description: A clear and concise description of the bug.
placeholder: Describe what happened...
validations:
required: true

- type: textarea
id: steps-to-reproduce
attributes:
label: Steps to Reproduce
description: List the steps to reproduce the behavior.
placeholder: |
1. Go to '...'
2. Click on '...'
3. See error
validations:
required: true

- type: textarea
id: expected-behavior
attributes:
label: Expected Behavior
description: What did you expect to happen?
placeholder: Explain what you expected to happen...
validations:
required: true

- type: dropdown
id: operating-system
attributes:
label: Operating System
description: What OS are you using?
options:
- Windows 10
- Windows 11
- macOS
- Linux (Ubuntu)
- Linux (Fedora)
- Linux (Arch)
- Linux (Other)
- Other
validations:
required: true

- type: input
id: version
attributes:
label: Version
description: What version of the software are you running?
placeholder: e.g., 1.1.0
validations:
required: true

- type: dropdown
id: browsers
attributes:
label: Browser (if applicable)
description: Which browser are you using?
multiple: true
options:
- Chrome
- Firefox
- Safari
- Edge
- Opera
- Other

- type: textarea
id: additional-context
attributes:
label: Additional Context
description: Add any other context, screenshots, or logs about the problem.
placeholder: Include screenshots, error messages, or any other relevant information...

- type: checkboxes
id: checklist
attributes:
label: Checklist
options:
- label: I have searched existing issues to avoid duplicates
required: true
- label: I have provided all required information
required: true
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: Security Issues
url: https://github.com/ErenayDev/checkpoint-ts/security/advisories/new
about: Report security vulnerabilities privately
- name: Discussions
url: https://github.com/ErenayDev/checkpoint-ts/discussions
about: Ask questions and discuss ideas
82 changes: 82 additions & 0 deletions .github/ISSUE_TEMPLATE/documentation.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
name: Documentation Update
description: Suggest updates or additions to documentation
title: "[Docs]: "
labels: ["documentation", "improvement"]
assignees: []
body:
- type: markdown
attributes:
value: |
Help us improve our documentation by suggesting updates or additions.

- type: dropdown
id: doc-type
attributes:
label: Documentation Type
description: What type of documentation needs updating?
options:
- README
- API Documentation
- Installation Guide
- User Guide
- Developer Guide
- Code Comments
- Other
validations:
required: true

- type: textarea
id: current-issue
attributes:
label: Current Issue
description: What's wrong with the current documentation?
placeholder: Describe what's missing, outdated, or unclear...
validations:
required: true

- type: textarea
id: suggested-changes
attributes:
label: Suggested Changes
description: What changes would you like to see?
placeholder: Provide detailed description of the changes...
validations:
required: true

- type: input
id: affected-sections
attributes:
label: Affected Sections
description: Which sections or files need updating?
placeholder: e.g., README.md section 3, API endpoint /users

- type: dropdown
id: urgency
attributes:
label: Urgency
description: How urgent is this documentation update?
options:
- Low - Nice to have
- Medium - Should be updated soon
- High - Needs immediate attention
- Critical - Blocking users
default: 1
validations:
required: true

- type: textarea
id: additional-resources
attributes:
label: Additional Resources
description: Any related links, examples, or resources?
placeholder: Include any relevant links, examples, or references...

- type: checkboxes
id: checklist
attributes:
label: Checklist
options:
- label: I have checked the current documentation
required: true
- label: I have searched for existing documentation issues
required: true
20 changes: 0 additions & 20 deletions .github/ISSUE_TEMPLATE/feature_request.md

This file was deleted.

76 changes: 76 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
name: Feature Request
description: Suggest a new feature or improvement
title: "[Feature]: "
labels: ["enhancement", "feature-request"]
assignees:
- ErenayDev
body:
- type: markdown
attributes:
value: |
Thank you for suggesting a new feature! Please provide as much detail as possible.

- type: textarea
id: feature-description
attributes:
label: Feature Description
description: What feature would you like to see?
placeholder: Describe the feature you'd like to request...
validations:
required: true

- type: textarea
id: problem-statement
attributes:
label: Problem Statement
description: What problem does this feature solve?
placeholder: Explain the problem or need for this feature...
validations:
required: true

- type: textarea
id: proposed-solution
attributes:
label: Proposed Solution
description: How should this feature work?
placeholder: Describe how this feature could be implemented...
validations:
required: true

- type: textarea
id: alternatives
attributes:
label: Alternative Solutions
description: Have you considered any alternative solutions?
placeholder: Describe any alternative solutions you've considered...

- type: dropdown
id: priority
attributes:
label: Priority
description: How important is this feature to you?
options:
- Low
- Medium
- High
- Critical
default: 1
validations:
required: true

- type: textarea
id: additional-context
attributes:
label: Additional Context
description: Add any other context, screenshots, mockups, or resources.
placeholder: Include any relevant screenshots, links, or resources...

- type: checkboxes
id: checklist
attributes:
label: Checklist
options:
- label: I have searched existing issues to avoid duplicates
required: true
- label: This feature aligns with the project's goals
required: true
14 changes: 14 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## Description
Explain the changes you made and why.

Fixes # (issue number)

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Documentation update

## Checklist
- [ ] Code follows project guidelines
- [ ] Tests added/updated
- [ ] Documentation updated
6 changes: 3 additions & 3 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ concurrency:
jobs:
fmt:
name: fmt
runs-on: ubuntu-latest
runs-on: self-hosted
steps:
Comment on lines +26 to 27
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

cat -n .github/workflows/ci.yml | head -70

Repository: ErenayDev/checkpoint-ts

Length of output: 2139


🏁 Script executed:

# Let me see more context around the test job to check if there are other self-hosted runners
cat -n .github/workflows/ci.yml | sed -n '66,100p'

Repository: ErenayDev/checkpoint-ts

Length of output: 776


Self-hosted runners on PR jobs are a security risk.

The fmt, clippy, and doc jobs run on self-hosted runners while the workflow is triggered by pull_request events, exposing runner hosts to untrusted PR code. Use GitHub-hosted runners for PR events or implement fork guards to prevent self-hosted execution on external contributions.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml around lines 26 - 27, The PR jobs `fmt`, `clippy`,
and `doc` currently use `runs-on: self-hosted` which exposes self-hosted runners
to untrusted PR code; update the workflow to use GitHub-hosted runners for
pull_request events (e.g., switch `runs-on` to a hosted label like
`ubuntu-latest` for those jobs) or add a fork-guard conditional so that when
`github.event_name == 'pull_request'` the `fmt`, `clippy`, and `doc` jobs do not
run on `self-hosted` (or are skipped) and only use self-hosted runners for
trusted events (push/main). Ensure the change targets the `fmt`, `clippy`, and
`doc` job blocks that contain `runs-on: self-hosted`.

- name: Checkout
uses: actions/checkout@v5
Expand All @@ -37,7 +37,7 @@ jobs:
run: cargo fmt -- --check
clippy:
name: clippy
runs-on: ubuntu-latest
runs-on: self-hosted
permissions:
contents: read
checks: write
Expand All @@ -54,7 +54,7 @@ jobs:
uses: clechasseur/rs-clippy-check@v5
doc:
name: doc
runs-on: ubuntu-latest
runs-on: self-hosted
steps:
- uses: actions/checkout@v5
- name: Install Rust nightly
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/codecov.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:

jobs:
coverage:
runs-on: ubuntu-latest
runs-on: self-hosted
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# First, let's look at the codecov.yml file structure
echo "=== Checking .github/workflows/codecov.yml ==="
if [ -f ".github/workflows/codecov.yml" ]; then
  cat -n ".github/workflows/codecov.yml"
else
  echo "File not found, checking for similar files..."
  fd -t f 'codecov' .github/workflows/ 2>/dev/null || echo "No codecov workflows found"
fi

Repository: ErenayDev/checkpoint-ts

Length of output: 1065


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Run the verification script from the review comment
# to identify workflows combining pull_request + self-hosted
fd -t f '.+\.ya?ml$' .github/workflows 2>/dev/null | while read -r wf; do
  if rg -l 'pull_request' "$wf" 2>/dev/null | grep -q .; then
    if rg -l 'self-hosted' "$wf" 2>/dev/null | grep -q .; then
      echo "=== Potentially unsafe workflow: $wf ==="
      echo "Lines with pull_request trigger:"
      rg -n 'pull_request' "$wf" 2>/dev/null || true
      echo ""
      echo "Lines with self-hosted:"
      rg -n 'self-hosted' "$wf" 2>/dev/null || true
      echo ""
      echo "Checking for fork detection guards:"
      rg -n "fork\|trusted\|if:" "$wf" 2>/dev/null || echo "No fork detection found"
      echo ""
    fi
  fi
done

Repository: ErenayDev/checkpoint-ts

Length of output: 1628


Do not execute untrusted PR jobs on self-hosted runners.

With on.pull_request (Line 6) and runs-on: self-hosted (Line 11), forked PR code can run on your infrastructure. This pattern exists in multiple workflows (codecov.yml, ci.yml, release.yml, web.yml) with no fork detection guards. Gate fork PRs or move PR jobs to GitHub-hosted runners.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/codecov.yml at line 11, The workflow currently allows
forked PRs to run on self-hosted runners because it uses on.pull_request and
runs-on: self-hosted; fix by preventing forked PRs from targeting your
self-hosted runner: either change the PR-targeted job to use GitHub-hosted
runners (e.g., replace runs-on: self-hosted with a hosted label) or add a
job-level guard that only runs when the pull request comes from the same repo
(use the GitHub context, e.g. an if condition like: github.event_name !=
'pull_request' || github.event.pull_request.head.repo.full_name ==
github.repository) so jobs defined where runs-on: self-hosted (referenced in
this file) refuse to execute for forked PRs.

steps:
- uses: actions/checkout@v4

Expand Down
Loading
Loading