Release Notes

From Obsidian Scheduler
Revision as of 01:29, 19 June 2025 by Craig (talk | contribs)
Jump to navigationJump to search

Please review our Upgrade Instructions.

Read about our Planned Releases.

Looking for old release notes? See Release Notes - Older Releases.

Obsidian 6.2.1

To Be Released June 2025

Bug Fixes

  • Certain recoveries greater than 24 hours using new day of month proximity patterns introduced in 6.2.0 would result in no jobs spawning.
  • Migrations targeting 6.0.0 and greater that start earlier than 5.0.0 skip the 5.0.0 migration. Migrating to any 5.x version first and then to 6.0.0 or later works around this issue.

Obsidian 6.2.0

Released May 2025

Features / Enhancements

Bug Fixes

  • Combination of table prefix, sorting by clob column and Oracle metadata load failure no longer results in sql error. This occurred in the UI when viewing raw job history results and in API calls for job runtime results.

Obsidian 6.1.1

Released March 2025

Features / Enhancements

Bug Fixes

  • Native authentication REST logins do not apply 'last login' timestamps. Avoids noisy error that was appearing in logs.

Obsidian 6.1.0

Released March 2025

Features / Enhancements

  • Native authentication now disables users after 4 invalid login attempts, either password or MFA code if applicable. Invalid attempts threshold is configurable.
  • Native authentication last login datetime displayed on list user screen.
  • Stronger licensing controls. Site and hardware licenses as of this version must be regenerated by Carfey Software and every 2 years. Contact us at licensing obsidianscheduler.com.

Bug Fixes

  • Native authentication password complexity pattern properly created and no longer overwritten on restart.

Obsidian 6.0.1

Released February 2025

Features / Enhancements

Bug Fixes

  • Native authentication user updates now support long passwords.

Obsidian 6.0.0

Released December 27, 2024

Features / Enhancements

  • Jakarta Servlet 5.0
    • Servlet container for Web Admin must support Jakarta Servlet 5.0 (e.g. Tomcat 10, Jetty 11)
  • Micronaut integration support
  • Groovy 4 support
  • Yaml configuration support[1]
  • Native authentication supports customizable password complexity requirements
  • XML support deprecated across the product including XML UI downloads, XML runner configurations and XML license leases.
    • Starting January 1st 2027, XML license lease requests will stop being processed. All Obsidian instances running using internet-verified licenses (including licence key proxies) will be required to use release 6.0.0 or later as of January 1st 2027.
    • Above noted XML support will be removed in the first Obsidian version released in 2027.
  • License leases use JSON payloads.

Obsidian 5.5.1

Released December 16, 2024

Bug Fixes

  • Admin only (no scheduler) UI no longer generates event hook errors while running nor during shutdown
  • Quick start installer file no longer generates errors during installation
  • A few small web UI enhancements

Obsidian 5.5.0

Released October 2024

Features / Enhancements

  • Event Hooks management available in UI, Embedded API and REST API.
  • Installer supports custom add on configurations Potential breaking change to automated installer files. [2]

Bug Fixes

  • Certain Cron expressions that fail to generate text descriptions no longer impact scheduling.
  • Text database columns were previously restricted to maximum length of MySQL implementation. Corrected to validate length via DB implementation.

Obsidian 5.4.0

Released June 2024

Features / Enhancements

Bug Fixes

  • Oracle identifier no longer too long when using prefixes.

Obsidian 5.3.0

Released March 2024

Features / Enhancements

Bug Fixes

Obsidian 5.2.1

Released January 2024

Features / Enhancements

Bug Fixes

  • Schedule descriptions are now updated after edits are applied in all UI screens and APIs.

Obsidian 5.2.0

Released December 2023

Features / Enhancements

Bug Fixes

  • Time picker buttons (hour, minute, AM/PM) in Job Activity filtering no longer change other elements of the selected time.
  • Cron pattern with LW and any other non-L value in day position no longer also incorrectly evaluates to last day.

Obsidian 5.1.1

Released June 2023

Bug Fixes

  • Native authentication no longer fails when user deletes are attempted from the UI.
  • Built in maintenance job Job History Cleanup no longer leaves deletion candidate CHAIN SKIPPED records in the JOB_HISTORY table in rare circumstances.

Obsidian 5.1.0

Released April 2023

Features / Enhancements

  • Schedule Aliases now support fragments for configuration-time substitutions.
  • New convenience job Database File Export Job for generating basic file extracts from database queries.
  • New convenience job REST Invocation Job for making simple REST calls and storing results.
  • Performance improvements in job failure handling.

Obsidian 5.0.4

Released February 2022

Features / Enhancements

  • Log4j2 2.17.1 as fix for RCE vulnerability where attackers can modify log4j configuration.
  • Restore missing default log4j2 configuration in installation artifacts.

Obsidian 5.0.3

Released December 2021

Features / Enhancements

  • Log4j2 2.17.0 as fix for DOS vulnerability
  • Fix native login issue showing as inactive on some databases.

Obsidian 5.0.2

Released December 2021

Features / Enhancements

Obsidian 5.0.1

Released December 2021

Features / Enhancements

Bug Fixes

  • Fix sporadic native login issue on some databases.
  • Formatting fix in quick installer file

Obsidian 5.0.0

Released August 2021.

Features / Enhancements

Footnotes

  1. If you are using automated installer files from previous releases, you will need to add an additional configuration item to choose between yaml and properties formats in UserInputPanel.0.
    <com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.0">
            <userInput>
    ......snip......
                <entry key="config.format" value="yaml" />
    OR
                <entry key="config.format" value="properties" />
    ......snip......
            </userInput>
        </com.izforge.izpack.panels.UserInputPanel>
    
  2. If you are using automated installer files from previous releases, you will need to add a new section of xml as of Obsidian 5.5.0 to handle a new UserInputPanel. Immediately after the UserInputPanel.17 closing brace, add the following:
    <com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.18">
    	<userInput>
    		<entry key="extra.log4j2.properties.1" value=""/>
    		<entry key="extra.log4j2.properties.2" value=""/>
    		<entry key="extra.log4j2.properties.3" value=""/>
    		<entry key="extra.log4j2.properties.4" value=""/>
    		<entry key="extra.log4j2.properties.5" value=""/>
    		<entry key="extra.log4j2.properties.6" value=""/>
    		<entry key="extra.log4j2.properties.7" value=""/>
    		<entry key="extra.log4j2.properties.8" value=""/>
    		<entry key="extra.log4j2.properties.9" value=""/>
    		<entry key="extra.log4j2.properties.10" value=""/>
    		<entry key="extra.log4j2.properties.11" value=""/>
    		<entry key="extra.log4j2.properties.12" value=""/>
    		<entry key="extra.log4j2.properties.13" value=""/>
    		<entry key="extra.log4j2.properties.14" value=""/>
    		<entry key="extra.log4j2.properties.15" value=""/>
    		<entry key="extra.log4j2.properties.16" value=""/>
    		<entry key="extra.log4j2.properties.17" value=""/>
    		<entry key="extra.log4j2.properties.18" value=""/>
    		<entry key="extra.log4j2.properties.19" value=""/>
    		<entry key="extra.log4j2.properties.20" value=""/>
    		<entry key="extra.carfey.properties.1" value=""/>
    		<entry key="extra.carfey.properties.2" value=""/>
    		<entry key="extra.carfey.properties.3" value=""/>
    		<entry key="extra.carfey.properties.4" value=""/>
    		<entry key="extra.carfey.properties.5" value=""/>
    		<entry key="extra.carfey.properties.6" value=""/>
    		<entry key="extra.carfey.properties.7" value=""/>
    		<entry key="extra.carfey.properties.8" value=""/>
    		<entry key="extra.carfey.properties.9" value=""/>
    		<entry key="extra.carfey.properties.11" value=""/>
    		<entry key="extra.carfey.properties.10" value=""/>
    		<entry key="extra.carfey.properties.12" value=""/>
    		<entry key="extra.carfey.properties.13" value=""/>
    		<entry key="extra.carfey.properties.14" value=""/>
    		<entry key="extra.carfey.properties.15" value=""/>
    		<entry key="extra.carfey.properties.16" value=""/>
    		<entry key="extra.carfey.properties.17" value=""/>
    		<entry key="extra.carfey.properties.18" value=""/>
    		<entry key="extra.carfey.properties.19" value=""/>
    		<entry key="extra.carfey.properties.20" value=""/>
    	</userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    
  3. If you are using automated installer files from previous releases and had email configured, you will need to add a new section of xml as of Obsidian 5.2.0 to handle a new UserInputPanel. Immediately after the UserInputPanel.16 closing brace, add the following:
    <com.izforge.izpack.panels.UserInputPanel id="UserInputPanel.17">
        <userInput>
            <entry key="mail.type.selection" value="javax"/>
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    
  4. There is a possibility of a breaking change to Embedded or REST API use due to the need to change the User Role enumeration from a Java enum to an enum-style class to support this feature. Bringing in the upgraded Obsidian library and compiling should reveal any such broken use of these enumerations. Needed changes should be minor and self-explanatory.