Versions and changelog

This documentation applies to iJob 1.0.0. The first formal release is available on GitHub Releases. Documentation changes and formal product releases are stated separately.

1.0.0 scope

Area Documented scope
Definitions and orchestration Task versions, workflow publication, dependencies, gateways and subjob references
Task capabilities SCRIPT, SQL, API_CALL, EVENT, DATA_CHECK, FILE_TRANSFER, PUSH, ETL, BATCH_ETL, SERVER_MONITOR, LOCAL_JAR
Execution Triggers, instances, topology, logs, inputs/outputs and run controls
Scheduling and administration Time schedules, calendars, routing, concurrency, resources, accounts and audit
Deployment Native Windows/Linux launchers, Linux Docker, standalone and cluster configuration

See each page for conditions and limitations. Product version 1.0.0, task/workflow definition versions, Local JAR protocol 1 and formal database installation migration V1 are separate identifiers.

First formal 1.0.0 release (2026-11-01)

The first formal installation starts with an empty database at V1. ijob-migration-tool, which converted development-era databases to V1, is no longer distributed. Do not start this application against an old database. Deployers must lawfully obtain MySQL Connector/J and Oracle JDBC/NLS and place them in the instance's external driver directory. PostgreSQL, SQL Server and SQLite drivers remain bundled. See platform databases.

Native installation requires user-provided Java 21 and OS dependencies. The Docker bundle targets Linux amd64; backend/Agent include Temurin 21.0.13+9 and Ubuntu 24.04 user space. Native installation is not restricted to Ubuntu; see runtime requirements.

Download inventory

File Purpose
ijob-1.0.0-native.zip / ijob-1.0.0-native.tar.gz Native programs; choose one archive format
ijob-1.0.0-docker.zip / ijob-1.0.0-docker.tar.gz Docker programs, templates and offline images; choose one archive format
ijob-1.0.0-source.zip Project source for this version, not a runtime bundle
ijob-1.0.0-third-party-sources.zip Matching applicable third-party corresponding source, patches and build materials
SHA256SUMS.txt SHA-256 values for six archives, release notes and release manifest

Runtime bundles contain both manuals and license notices. Matching third-party source must be available from the same release download location at no additional charge. Download the complete nine-file set from the v1.0.0 Release.

On Linux, run sha256sum --check --ignore-missing SHA256SUMS.txt to verify the files you downloaded. In PowerShell, compare Get-FileHash -Algorithm SHA256 <downloaded-file> with the inventory before extraction. Do not mix identically named files from different candidates. SHA-256 checks byte integrity; it is not a digital signature.

Feedback and security vulnerabilities

The source repository is public. Use GitHub Issues for general questions, ordinary bugs and feature requests, and the enabled GitHub private vulnerability reporting for security vulnerabilities. Sign in to GitHub to submit a report. No separate reporting mailbox is used. Download runtime bundles, matching third-party source and checksums from the v1.0.0 Release.

For general feedback, include the version, operating system, deployment method, reproduction steps, expected versus actual results and redacted logs. Submit vulnerabilities privately through Security and quality → Report a vulnerability, including affected versions, impact and reproduction. Do not post vulnerability details in public issues, pull requests or comments, or submit real passwords, tokens, private keys, databases or complete configurations. If the reporting button is absent, do not disclose vulnerability details in a public issue instead.

Known risks and validation scope

The local review as of 2026-11-01 retains known scan findings: 31 Ubuntu package-level findings in each backend/Agent image (27 MEDIUM, 4 LOW; 24 distinct CVEs across both), with no fixed versions available through the official updates checked then. These packages are distributed inside the images and remain in scope even though users supply their hosts. The web image had zero findings in this scan.

Spring MVC CVE-2026-47884 and CVE-2026-47890 retain their raw CRITICAL scanner ratings. Current route assertions found no related XSLT/implicit views or SSE fragment features; that is not a patch. MyBatis shaded OGNL CVE-2026-113730 is MEDIUM. A MyBatis upgrade produced an actual pagination incompatibility with the current PageHelper, so the verified version and risk record remain. Do not describe these findings as fixed or claim zero vulnerabilities. The release review used Trivy 0.76.1 and the vulnerability database updated on 2026-11-01. The verified 2026-10-31 Java identification index was reused before its NextUpdate. See the formal release notes for scope.

1.0.0 is released. See the formal release notes for validation scope and known risks; unexecuted tests are not passes.

Documentation update: 2026-10-31

  • Added order reconciliation, difference approval, quality blocking, report delivery and receiver monitoring extensions.
  • Moved order fixture data and receiver code into a companion setup page.
  • Corrected installation and quickstart instructions, unified footers, and tightened homepage and inline search spacing.
  • Product version remains 1.0.0.

The tutorials are also grouped into a learning path. The 17 scenarios include concrete SSH/SFTP, Kafka and email, trusted JAR, missed-run recovery, shared concurrency and configuration-transfer steps. New bilingual screenshots show actual runs; execution success, data quality, message delivery and metric health are checked separately.

Documentation update: 2026-10-29

  • Added core concepts, a glossary, variable expressions, first initialization and runtime requirements.
  • Added a role/action matrix and explained templates versus execution snapshots.
  • Organized plugin fields and separated UI initial values from server omission behavior.
  • Restructured scenarios as steps with expected results, troubleshooting and cleanup.
  • Added version paths, bilingual navigation and local search; improved screenshot presentation on the website.

These are website/documentation changes, not a new product release or proof that new steps ran against every external environment.

The documentation site identifies its current version and uses version-specific paths. Existing unversioned links remain accessible. When a later product version is established, retain 1.0.0 pages and identify applicable or evidence-backed introduction versions. Do not offer incorrect language/version links for missing pages.

Bundles and upgrades

For a formal bundle, verify its manifest, SHA256SUMS.txt, platforms and release notes. Files sharing version 1.0.0 need not be byte-identical. Read backup/restore and upgrade/rollback before upgrading.

Core concepts · Runtime requirements · Manual index

Documentation version 1.0.0. Replace sample paths, resources and ports with those of your own environment.