# openplc-editor

**Repository Path**: galaxy_0/openplc-editor

## Basic Information

- **Project Name**: openplc-editor
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: GPL-3.0
- **Default Branch**: development
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-12-29
- **Last Updated**: 2026-03-02

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Open PLC Editor - IDE

![GitHub stars](https://img.shields.io/github/stars/Autonomy-Logic/openplc-editor?color=fa6470)
![GitHub issues](https://img.shields.io/github/issues/Autonomy-Logic/openplc-editor?color=d8b22d)

<p align="center">
<img alt="draft-cover" src="assets/images/github-background.png">
</p>

## Running a preview version

In order to run the development version, clone the repository, and install dependencies via `npm`, you need network access.

You'll need the following tools:

- [Git](https://git-scm.com/)
- [NodeJS](https://nodejs.org/en/download/), **x64**, version `>=20`

### Step by step

- Clone the repository locally and go to the project folder.

```bash
git clone https://github.com/Autonomy-Logic/openplc-editor.git

cd openplc-editor
```

- Install the dependencies

```bash
npm install
```

- Run the development script

```bash
npm run start:dev
```

## Releasing a New Version

The project uses GitHub Actions to automatically build and release new versions for all supported platforms (macOS, Windows, and Linux) in both x64 and ARM64 architectures.

### Creating a Release

To create a new release, simply create and push a new tag with the version number:

```bash
git tag v4.2.0
git push origin v4.2.0
```

This will automatically:
1. Build the application for all platforms (macOS, Windows, Linux) and architectures (x64, ARM64)
2. Sign and notarize the macOS builds
3. Create a GitHub Release with all artifacts attached
4. Generate release notes based on commits since the last release

### Version Naming

- Use semantic versioning: `vMAJOR.MINOR.PATCH` (e.g., `v4.2.0`)
- For pre-releases, add a suffix: `v4.2.0-beta`, `v4.2.0-alpha`, or `v4.2.0-rc1`
- Pre-release tags will be marked as pre-releases on GitHub

### Manual Workflow Trigger

You can also trigger the build workflow manually from the GitHub Actions tab without creating a release. This is useful for testing builds:

1. Go to Actions > Build and Release
2. Click "Run workflow"
3. Optionally specify a version number
4. Click "Run workflow"

Note: Manual triggers will build all artifacts but won't create a GitHub Release (releases are only created when pushing a tag).

## Documentation

Please go to the repository [wiki](https://github.com/Autonomy-Logic/openplc-editor/wiki) page to get instruction about the project.

## Project Management

Go to [project](https://github.com/orgs/Autonomy-Logic/projects/4) management page to see the current state of the project.

## Issues

Go to [issues](https://github.com/Autonomy-Logic/openplc-editor/issues) page to view the current state of issues in the project.