Skip to content

Release 1.0.14 with Bugfixes - #67

Merged
swittlich merged 8 commits into
mainfrom
dev
Aug 21, 2026
Merged

Release 1.0.14 with Bugfixes #67
swittlich merged 8 commits into
mainfrom
dev

Conversation

@swittlich

Copy link
Copy Markdown
Contributor

Pull Request

Describe your changes

Please include a summary of the change and which issue is fixed.

Issue ticket number and link

Fixes #xxx

Type of change

  • 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)
  • Documentation update
  • Security hardening / Infrastructure update

Verification & Release Checklist

1. Code Quality & Standards

  • I have performed a self-review of my code.
  • I have verified that the code compiles with zero warnings (dotnet build -c Release -warnaserror).
  • I have verified that NuGet dependency audits pass without High/Critical alerts.
  • I have successfully run dotnet test locally and all tests pass.

2. Thread Safety & Concurrency

  • I have verified that all UI modifications from background tasks/timers run on Dispatcher.UIThread.
  • I have ensured thread-safe access to cached models using atomic locking patterns.
  • I have utilized cancel-safe async logic and avoided finally-block cancellation leaks.

3. Memory & Resource Management

  • I have checked for and eliminated potential memory leaks from event handler subscriptions.
  • I have used weak references (WeakReference<T>) for transient/modal control tracking.
  • I have verified that all rented arrays (e.g. ArrayPool<T>) are cleared and returned in finally blocks.

4. Nullity & Safety Guarding

  • I have guarded against NullReferenceException on collection bounds and API results.
  • I have verified timeout-safe regex evaluations.
  • I have verified that file picker paths are checked for traversal and access safety.

5. Native AOT Compliance

  • I have avoided using dynamic reflection or dynamic JSON deserialization that violates AOT compilation.

6. Security Sandboxing

  • Security: If modifying Dockerfiles, I have ensured least-privilege execution (USER oneware).
  • Security: I have verified no sensitive credentials or daemon sockets are leaked in telemetry or volume mounts.

dependabot Bot and others added 8 commits July 20, 2026 17:55
Bumps the docker-dependencies group in /docker/oss-cad-suite with 1 update: ubuntu.


Updates `ubuntu` from `b7f4819` to `3131b4c`

---
updated-dependencies:
- dependency-name: ubuntu
  dependency-version: 3131b4cc82a783df6c9df078f86e01819a13594b865c2cad47bd1bca2b7063bb
  dependency-type: direct:production
  dependency-group: docker-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Bump version to 1.0.14 (csproj, oneware-extension.json) and add the
changelog entry for the DockerExecutionStrategy decomposition into
single-responsibility collaborators (already implemented in 66cfb17).
Behavior, public surface, and security gates are unchanged.
…-suite/dev/docker-dependencies-6e05db66b9

deps(docker): bump ubuntu from `b7f4819` to `3131b4c` in /docker/oss-cad-suite in the docker-dependencies group
@swittlich
swittlich merged commit db2cc22 into main Aug 21, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant