2027 Early Access SDK Artifacts?

Any ETA for early access SDK artifacts?

I’d love to peruse some Javadocs.

1 Like

Me too!

By end of day today (Wednesday) according to infra team.

4 Likes

I think all the bits save Web UI Component Storybooks are up, knock on wood. One more post incoming ...

Developing Against Ignition 2027.2.0-beta1

Beta SDK dependencies are available starting Wednesday, November 4.

These artifacts are published to nexus.inductiveautomation.com like SDK artifacts for regular releases.

  • Beta APIs should stay stable and non-breaking. A significant issue may still force a breaking change.
  • Beta versions are fixed prerelease versions, like -rc<n>. They are not -SNAPSHOT versions.
  • The suffix increments with each beta: -beta1, then -beta2, and so on.
  • Artifacts live in the standard release repositories. There is no beta-specific repository.

Gradle (Kotlin DSL)

Add the repository in build.gradle.kts, or in settings.gradle.kts under dependencyResolutionManagement.repositories:

repositories {
    maven {
        name = "inductiveautomation-releases"
        url = uri("https://nexus.inductiveautomation.com/repository/inductiveautomation-releases/")
    }
}

Declare dependencies with the SDK group com.inductiveautomation.ignitionsdk:

val ignitionVersion = "2027.2.0-beta1"
val gatewayApi = "com.inductiveautomation.ignitionsdk:gateway-api:$ignitionVersion"

dependencies {
    compileOnly(gatewayApi)
    testImplementation(gatewayApi)
}

Maven

Add the repository to pom.xml:

<repository>
    <id>ia-releases</id>
    <url>https://nexus.inductiveautomation.com/repository/inductiveautomation-releases</url>
    <snapshots>
        <enabled>false</enabled>
    </snapshots>
</repository>

Declare dependencies with provided scope:

<dependency>
    <groupId>com.inductiveautomation.ignitionsdk</groupId>
    <artifactId>gateway-api</artifactId>
    <version>2027.2.0-beta1</version>
    <scope>provided</scope>
</dependency>

npm / Yarn

Configure .yarnrc.yml:

npmScopes:
  inductiveautomation:
    npmRegistryServer: "https://nexus.inductiveautomation.com/repository/inductiveautomation-node-packages/"

Add the packages to package.json:

{
  "dependencies": {
    "@inductiveautomation/ignition-web-ui": "2027.2.0-beta1",
    "@inductiveautomation/perspective-client": "2027.2.0-beta1"
  }
}
3 Likes

Ignition SDK examples repo now has an ignition-2027 branch with all the updates needed to make them compile. Have not yet tried to install or run any of them :upside_down_face:

1 Like

Posting this here for my own future reference lol

2 Likes

I pretty-pleased:
https://sdk.inductiveautomation.com/javadoc/ignition2027/latest/index.html

3 Likes

I do that all the time. It's way easier to search the forum for your own answer to the question you forgot the answer for than to remember things.

:slight_smile:

1 Like

I'll add a general note here, because we haven't really come up with a great place for this:
Don't expect perfect stability for the API if you're choosing to start developing against beta, especially anything related to AI integration. Some aspects of that are pretty solid, and some aspects of that are extremely fluid. The AI landscape is such quicksand that we might reserve the right to make 'breaking' changes to AI interfaces even in monthly 2027.x releases.

1 Like

How stable-ish is the new Perspective component script extension feature? :eyes:

Let's call it an 8/10?
We're definitely going to have some similar/compatible API, because we're using it first party for the local tools declaration on the chat component. The exact API shape may change slightly, but the general idea (you shove JSON keys of your own to 'hang off' our shape) won't change significantly.

1 Like

The current npm packages list their own dependencies as 2027.2.0, which isn't published yet.

As a workaround, you can force use the available version through a resolutions block in your package.json:

   "dependencies": {
        "@inductiveautomation/perspective-client": "2027.2.0-beta1",
        "@inductiveautomation/perspective-components": "2027.2.0-beta1",
        "@inductiveautomation/perspective-designer": "2027.2.0-beta1",
        "@inductiveautomation/perspective-drawing-common": "2027.2.0-beta1"
   },
   "resolutions": {
        "@inductiveautomation/perspective-client": "2027.2.0-beta1",
        "@inductiveautomation/perspective-common": "2027.2.0-beta1",
        "@inductiveautomation/perspective-drawing-common": "2027.2.0-beta1"
    }

Yarn will complain, but it works:

warning Resolution field "@inductiveautomation/perspective-common@2027.2.0-beta1" is incompatible with requested version "@inductiveautomation/perspective-common@2027.2.0"
warning Resolution field "@inductiveautomation/perspective-client@2027.2.0-beta1" is incompatible with requested version "@inductiveautomation/perspective-client@2027.2.0"
warning Resolution field "@inductiveautomation/perspective-drawing-common@2027.2.0-beta1" is incompatible with requested version "@inductiveautomation/perspective-drawing-common@2027.2.0"

Phew. Glad that resolutions hack works, sad it is necessary in the first place.

I have a ticket to fix this upstream. My front end build knowledge is weaker than my back end build knowledge, and I'm not sure of the appetite for rewiring these interdependencies during -beta<n> or -rc<n> windows.

That said final release is months out so maybe?

1 Like

It’s kind of a wonky problem. I wouldn’t even know how to introduce this error in a Yarn workspace, unless there was some manual re-versioning going on before publishing…