Changelog
2.0
2.0.0
Release date: 11.07.2025
⚠️ Note that the following io.Manager NPM packages will now be published in the public NPM registry:
@interopio/manager
as of version2.0.0
;@interopio/manager-admin-ui
as of version3.0.0
;Previous versions of the packages will still be available in the private JFROG registry.
Breaking Changes
ℹ️ For more details on the breaking changes and the required migration steps, see also the Upgrade section.
⚠️ Note that as of version 2.0.0, io.Manager requires a license key to operate. To acquire a license key, contact us at
sales@interop.io
. Existing customers should contact their Client Success representative to obtain a license key.ℹ️ For more details on licensing, see the Requirements > Licensing section.
- Added a required
licenseKey
top-level property in the configuration object for initializing the io.Manager Server. Use this property to supply your io.Manager license key:
import { start } from "@interopio/manager"; const config = { // It's now required to provide a valid license key for io.Manager to operate. licenseKey: "my-license-key" }; const server = await start(config);
You can also use the
API_LICENSE_KEY
environment variable:API_LICENSE_KEY=my-license-key
- Dropped Node.js 18 support. io.Manager now requires Node.js 20 LTS or 22 LTS.
- The default value for
skipProcessExitOnStop
is changed totrue
. If you wantprocess.exit()
to be called whenserver.stop()
is called or when the server fails to start, setskipProcessExitOnStop
tofalse
.- Removed the
store
property of theServer
interface.- Removed the
UserStore
,Store
, andBLOBStore
interfaces.- TypeScript types:
- The
AuditService.getAll()
method now returnsAuditLogDataResult
instead ofDataResult<AuditLog>
.- When implementing
CustomAuthenticator
, you now have to import the following types from@interopio/manager
instead of@interopio/manager-api
:
Token
User
- When implementing
AuditService
, you now have to import the following types from@interopio/manager
instead of@interopio/manager-api
:
AuditLog
AuditLogDataResult
CleanAuditLogRequest
DataRequest
User
- When implementing
GroupsService
, you now have to import the following types from@interopio/manager
instead of@interopio/manager-api
:
DataRequest
Group
GroupDataResult
GroupsFeatures
User
- The types
AuditLogEntityType
andAuditLogOperation
have been converted from TypeScript Union types to TypeScript Enums.- Removed the previously deprecated
status_endpoint
top-level configuration property.- The
GET /db
endpoint now always returns a500
status code regardless of the configured database. Previously, this only worked for MongoDB and returned database statistics specific to MongoDB.- Removed
false
,"none"
, and"sentry"
as values for themonitoring
property. Use{ type: "none" }
or{ type: "sentry" }
instead.- Removed the
tracesSampleRate
property from the Sentry monitoring configuration. UsesentryOptions.tracesSampleRate
instead.- Removed the
dsn
property from the Sentry monitoring configuration. UsesentryOptions.dsn
instead.- Tracing via the Sentry SDK is no longer supported. The recommended way to send traces to Sentry is by using OpenTelemetry traces. See also the OpenTelemetry with Sentry example on GitHub.
- Removed
["admin"]
as a default value for theAPI_AUTH_EXCLUSIVE_USERS
environment variable. This change doesn't affect users who don't use environment variables for configuring io.Manager as the default value was valid only for theAPI_AUTH_EXCLUSIVE_USERS
environment variable.- Due to a change in the FDC3 specification, the
name
anddefinition.name
app properties won't be checked for consistency for FDC3 app definitions. Thename
anddefinition.appId
properties will still be checked. For more details, see the FDC3 Standard 2.1.- When using environment variable configuration with
.env
files, values from the.env
files will override the process environment variables. This means that if an environment variable is both defined in the.env
file and passed to the process, the value from the.env
file will be used.New Features
- Added OpenAPI 3.0.0 support via Swagger UI.
- Added a
traceContext
database column to thecommands
table (for PostgreSQL and Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must create the
traceContext
column manually by running the following scripts.For PostgreSQL:
ALTER TABLE commands ADD COLUMN IF NOT EXISTS "traceContext" JSON;
For Microsoft SQL Server:
IF NOT EXISTS ( SELECT * FROM sys.columns WHERE object_id = OBJECT_ID(N'[dbo].[commands]') AND name = 'traceContext' ) ALTER TABLE commands ADD traceContext NVARCHAR(MAX);
- Changed the type of the
commandParams
database column of thecommands
table toJSON
(for PostgreSQL only).⚠️ Note that users who don't use automatic schema migration must change the type of the
commandParams
column manually by running the following script:
ALTER TABLE commands ALTER COLUMN "commandParams" TYPE JSON USING "commandParams"::json;
- Changed the precision of the
weight
database column in theglue42SystemConfig
table (for PostgreSQL and Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must change the precision of the
weight
column manually by running the following scripts.For PostgreSQL:
ALTER TABLE "glue42SystemConfig" ALTER COLUMN weight TYPE numeric(8, 6) USING weight::numeric(8, 6);
For Microsoft SQL Server:
ALTER TABLE glue42SystemConfig ALTER COLUMN weight decimal(8, 6);
- Changed the type of the
definition
database column of thelayouts
table toJSON
(for PostgreSQL and Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must change the type of the
definition
column manually by running the following scripts.For PostgreSQL:
ALTER TABLE layouts ALTER COLUMN definition TYPE JSON USING definition::json;
For Microsoft SQL Server:
ALTER TABLE layouts ALTER COLUMN definition NVARCHAR(max) NOT NULL;
- Changed the type of the
comment
database column of thecrashes
table toNVARCHAR(max)
(for Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must change the type of the
comment
column manually by running the following script:
ALTER TABLE crashes ALTER COLUMN comment NVARCHAR(max);
- Changed the types of the
comment
,description
andattachment
database columns of thefeedback
table toNVARCHAR(max)
(for Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must change the type of the columns manually by running the following script:
ALTER TABLE feedback ALTER COLUMN comment NVARCHAR(max); ALTER TABLE feedback ALTER COLUMN description NVARCHAR(max) NOT NULL; ALTER TABLE feedback ALTER COLUMN attachment NVARCHAR(max) NOT NULL;
- Added an
auth_timeout
top-level key in the configuration object for initializing the io.Manager Server, which accepts a number as a value and defaults to120000
. Use this property to specify an interval in milliseconds to wait for the authentication process request to complete before rejecting it. This setting is useful when you have implemented a custom authentication mechanism:
import { start } from "@interopio/manager"; import { MyAuthenticator } from "./MyAuthenticator"; const config = { auth_method: "custom", auth_custom: new MyAuthenticator(), auth_timeout: 60000 }; const server = await start(config);
You can also use the
API_AUTH_TIMEOUT
environment variable:
API_AUTH_TIMEOUT=60000
Added a
cors
top-level key in the configuration object for initializing the io.Manager Server. The value will be passed to thecors
middleware. For more details, see the Configuration Options section in thecors
package documentation.Added an
interceptProcessSignals
top-level key in the configuration object for initializing the io.Manager Server. If set totrue
, io.Manager will listen for the following signals:"SIGINT"
,"SIGTERM"
,"SIGHUP"
,"SIGBREAK"
,"SIGQUIT"
. Defaults tofalse
. You can also use theAPI_INTERCEPT_PROCESS_SIGNALS
environment variable.Added new properties to the
purge
top-level key in the configuration object for initializing the io.Manager Server. Use these properties to configure the data purging functionality of io.Manager:
Property Type Description purgeCommandsAfterDays
number
Number of days after which an executed command and the respective command result become eligible for purging. Set to -1
to disable purging of commands and command results. Defaults to90
.scheduledTaskInterval
number
Interval in milliseconds at which to run the periodic data purging operation. Defaults to 86400000
(1 day).You can also use the following environment variables:
Environment Variable Description API_PURGE_COMMANDS_AFTER_DAYS
Number of days after which an executed command and the respective command result become eligible for purging. Set to -1
to disable purging of commands and command results. Defaults to90
.API_PURGE_SCHEDULED_TASK_INTERVAL
Interval in milliseconds at which to run the periodic data purging operation. Defaults to 86400000
(1 day).
Added a
sentryClient
property to theSentryMonitoringConfig
object. Use to provide an already initialized Sentry client. Useful if you want to initialize Sentry manually before starting io.Manager. For more details, see the Sentry for Node.js guide in the official Sentry documentation.Added a
sentryOptions
property toSentryMonitoringConfig
object. Passed to theSentry.init()
method. Ignored when a Sentry client is provided via thesentryClient
property. For more details, see the Configuration Options section in the official Sentry documentation.Added a
customPropagator
property toOtelTracingConfig
object. Use to provide a custom OpenTelemetry propagator.Added a
customContextManager
property toOtelTracingConfig
object. Use to provide a custom OpenTelemetry context manager.Added a new
API_LOG_LEVEL
environment variable. Use to set thelog4js
log level when using environment variable configuration. Defaults toinfo
.Improvements & Bug Fixes
- Added a new
CustomAuthUnauthorizedError
export. Used in custom authenticator implementations.- Added a new
OtelConfig
export. Exports the existing OpenTelemetry configuration type.- The
name
top-level configuration property is now optional. If not provided, the server will use the default value of"local"
.- The
port
top-level configuration property is now optional. If not provided, the server will use the default value of4356
.Deprecated Endpoints
The following REST API endpoints have been deprecated:
Deprecated Endpoint New Endpoint GET /db
Use GET /db-connectivity
instead.GET /server/info
Use GET /v2/server/info
instead.Dependency Changes
The following new dependencies were added to the package:
@nestjs/common
version^11.1.0
@nestjs/core
version^11.1.0
@nestjs/platform-express
version^11.1.0
@nestjs/swagger
version^11.2.0
@opentelemetry/instrumentation-nestjs-core
version^0.46.0
mime
version^1.6.0
rxjs
version^7.8.2
tedious
version^18.6.1
The following dependencies were removed from the package:
@interopio/manager-api
@sentry/tracing
@types/bcryptjs
@types/cookie-parser
@types/lodash
@types/multer
@types/shortid
ajv
cross-env
The following dependencies were updated:
@interopio/otel
from version^0.0.14
to^0.0.67
@interopio/schemas
from version^9.2.0
to^9.7.0
@okta/jwt-verifier
from version^3.1.0
to^4.0.1
@opentelemetry/api-logs
from version^0.54.0
to^0.200.0
@opentelemetry/exporter-logs-otlp-http
from version^0.54.0
to^0.200.0
@opentelemetry/exporter-metrics-otlp-http
from version^0.54.0
to^0.200.0
@opentelemetry/exporter-trace-otlp-http
from version^0.54.0
to^0.200.0
@opentelemetry/instrumentation
from version^0.54.0
to^0.200.0
@opentelemetry/instrumentation-express
from version^0.43.0
to^0.49.0
@opentelemetry/instrumentation-http
from version^0.54.0
to^0.200.0
@opentelemetry/instrumentation-knex
from version^0.40.0
to^0.45.0
@opentelemetry/instrumentation-mongodb
from version^0.47.0
to^0.53.0
@opentelemetry/instrumentation-undici
from version^0.6.0
to^0.11.0
@opentelemetry/resources
from version^1.27.0
to^2.0.0
@opentelemetry/sdk-logs
from version^0.54.0
to^0.200.0
@opentelemetry/sdk-metrics
from version^1.27.0
to^2.0.0
@opentelemetry/sdk-trace-base
from version^1.27.0
to^2.0.0
@opentelemetry/sdk-trace-node
from version^1.27.0
to^2.0.0
@opentelemetry/semantic-conventions
from version^1.27.0
to^1.33.0
@sentry/node
from version^7.13.0
to^9.18.0
bcryptjs
from version^2.4.3
to^3.0.2
cookie-parser
from version^1.4.6
to^1.4.7
dotenv
from version^16.4.5
to17.0.0
express
from version^4.17.1
to^5.1.0
express-oauth2-jwt-bearer
from version^1.4.1
to^1.6.1
jsonwebtoken
from version^9.0.0
to^9.0.2
knex
from version^2.4.1
to^3.1.0
mongodb
from version^4.11.0
to^6.16.0
mssql
from version^9.1.1
to^11.0.1
multer
from versionnpm:@interopio/multer@^1.4.5-lts.1
tonpm:@interopio/multer@^2.0.0
pg
from version^8.7.3
to^8.16.0
reflect-metadata
from version^0.1.13
to^0.2.2
semver
from version^7.5.2
to^7.7.2
shortid
from version^2.2.8
to^2.2.17
1.0
1.8.2
Release date: 27.03.2025
Improvements & Bug Fixes
- Removed the "user" field from the
serverx-token
header passed from io.Connect to io.Manager.
1.8.1
Release date: 26.02.2025
Improvements & Bug Fixes
- It's now possible to define custom status messages for health checks:
- Added a
healthCheckStatus
optional string property to theHealthEndpointsConfig
object. The string will be passed as a value to the"status"
field in the health check response. You can also use theAPI_HEALTH_ENDPOINTS_CUSTOM_HEALTHCHECK_STATUS
environment variable.- Added a
databaseHealthCheckStatus
optional string property to theHealthEndpointsConfig
object. The string that the database connectivity health check will return as a successful response. You can also use theAPI_HEALTH_ENDPOINTS_CUSTOM_DB_CONNECTIVITY_STATUS
environment variable.
1.8.0
Release date: 24.02.2025
New Features
- Implemented additional health check endpoints on custom routes:
- Added a
customHealthCheckRoute
optional string property to theHealthEndpointsConfig
object. If present, an additional health check endpoint will be available on the specified route. You can also use theAPI_HEALTH_ENDPOINTS_CUSTOM_HEALTHCHECK_ROUTE
environment variable.- Added a
customDatabaseHealthCheckRoute
optional string property to theHealthEndpointsConfig
object. If present, an additional database health check endpoint will be available on the specified route. You can also use theAPI_HEALTH_ENDPOINTS_CUSTOM_DB_CONNECTIVITY_HEALTHCHECK_ROUTE
environment variable.
1.7.4
Release date: 20.02.2025
Improvements & Bug Fixes
- Relaxed the
DataRequest
JSON filter validation to safely allow using arbitrary JSON fields.
1.7.3
Release date: 20.11.2024
Improvements & Bug Fixes
- Fixed a bug where sometimes the io.Manager Server would fail to load environment variables from a file.
1.7.2
Release date: 19.11.2024
Improvements & Bug Fixes
- Added consistency validation for apps:
name
anddefinition.name
must be the same;name
anddefinition.appId
(if present) must be the same;- Added consistency validation for Layouts:
name
anddefinition.name
must be the same;type
anddefinition.type
must be the same;
1.7.1
Release date: 07.11.2024
New Features
- Exposed
appsV2
andlayoutsV2
via theServer
interface for custom scripts.Improvements & Bug Fixes
- Fixed a bug where some PostgreSQL queries wouldn't use the correct schema.
1.7.0
Release date: 01.11.2024
New Features
- Added OpenTelemetry support.
- Added new environment variable
API_MONITORING_SENTRY_DSN
- custom Sentry DSN to use when using monitoring via Sentry.- Added new environment variable
API_AUTH_AUTH0_ISSUER_BASE_URL
for Auth0 authentication - base URL for the Auth0 issuer.- Added database connectivity health check as well as Docker health checks for the io.Manager Server and Admin UI Docker images.
- Added a
purgeAtStartupEnabled
optional Boolean property to thePurgeConfig
object. If set totrue
(default), will run the purge task at startup of the io.Manager Server. You can also use theAPI_PURGE_AT_STARTUP_ENABLED
environment variable to configure the purge behavior.- Added database column
others
to thelast_updated
table (for PostgreSQL and Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must create the
others
column manually by running the following scripts.For PostgreSQL:
ALTER TABLE last_updated ADD COLUMN IF NOT EXISTS others JSON NULL;
For Microsoft SQL Server:
IF NOT EXISTS ( SELECT * FROM sys.columns WHERE object_id = OBJECT_ID(N'[dbo].[last_updated]') AND name = 'others' ) ALTER TABLE last_updated ADD others NVARCHAR(MAX);
1.6.4
Release date: 11.09.2024
Improvements & Bug Fixes
- Fixed a bug where io.Manager would fail to save a crash dump generated by io.Connect Desktop.
1.6.3
Release date: 10.09.2024
Improvements & Bug Fixes
- Fixed a bug where invoking controllers directly via the
RestServer
class would throw an error.
1.6.2
Release date: 05.09.2024
Improvements & Bug Fixes
- Moved
dotenv
package from"devDependencies"
to"dependencies"
to fix a bug introduced in v1.6.0.
1.6.1
Release date: 04.09.2024
Improvements & Bug Fixes
- Fixed a bug where the total record count wasn't calculated correctly for data requests to PostgreSQL and Microsoft SQL Server.
1.6.0
Release date: 29.08.2024
New Features
- Implemented automatic failover when using PostgreSQL databases with io.Manager. To specify multiple PostgreSQL hosts, use the
hosts
property of thestore
object for configuring the connection to a PostgreSQL database. Thehosts
property accepts an array of objects describing PostgreSQL database hosts that will be tried in the order they are provided.The following example demonstrates configuring io.Manager Server to use multiple PostgreSQL hosts:
import { start } from "@interopio/manager"; // Configuration for the io.Manager Server. const config = { name: "my-server", port: 4242, token: { secret: "my-secret" }, // Configuration for connecting to a PostgreSQL database. store: { type: "postgresql", // Specifying multiple PostgreSQL hosts to which to connect. hosts: [ { connection: "postgresql://my_user:password@localhost:5432", dbName: "my_db", schemaName: "my_schema" }, { connection: "postgresql://my_user:password@localhost:5433", dbName: "my_db", schemaName: "my_schema", // io.Manager won't attempt to execute write operations on this host. isReadOnly: true } ] } }; // Initializing the io.Manager Server. const server = await start(config);
Improvements & Bug Fixes
- Added database column
browser
to themachines
table (for PostgreSQL and Microsoft SQL Server only).⚠️ Note that users who don't use automatic schema migration must create the
browser
column manually by running the following scripts.For PostgreSQL:
ALTER TABLE machines ADD COLUMN IF NOT EXISTS browser JSON NULL;
For Microsoft SQL Server:
IF NOT EXISTS ( SELECT * FROM sys.columns WHERE object_id = OBJECT_ID(N'[dbo].[machines]') AND name = 'browser' ) ALTER TABLE machines ADD browser NVARCHAR(MAX);
- Fixed a bug that would prevent MongoDB users from seeing feedback in the feedback list in the io.Manager Admin UI.
- Layouts can now be filtered by the
id
field using the Admin API.
1.5.0
Release date: 16.08.2024
New Features
- New REST API endpoints have been added:
New Endpoint Description GET /v2/server/info
Returns information about the io.Manager Server, such as server version and available capabilities. POST /v2/apps/add
Creates a new app definition or returns status code 400
if an app definition with the samename
property already exists. Returns the created app definition.POST /v2/apps/add-or-update
Creates a new app definition or updates an existing one if an app definition with the same name
property already exists. Returns the created or updated app definition.POST /v2/apps/update
Updates an app definition or returns status code 404
if an app definition with the specifiedname
property isn't found. Returns the updated app definition.POST /v2/layouts/add
Creates a new Layout definition or returns status code 400
if a Layout definition with the same combination ofname
,type
andowner
properties already exists. Returns the created Layout definition.POST /v2/layouts/add-or-update
Creates a new Layout definition or updates an existing one if a Layout definition with the same id
property (or the same combination ofname
,type
andowner
properties ifid
isn't provided) already exists. Returns the created or updated Layout definition.POST /v2/layouts/update
Updates a Layout definition or returns status code 404
if a Layout definition with the specifiedid
property (or the specified combination ofname
,type
andowner
properties ifid
isn't provided) isn't found. Returns the updated Layout definition.Deprecated Endpoints
The following REST API endpoints have been deprecated:
Deprecated Endpoint New Endpoint POST /apps
Use POST /v2/apps/add-or-update
instead.POST /apps/:name
Use POST /v2/apps/update
instead.POST /layouts
Use POST /v2/layouts/add-or-update
instead.POST /users/:name/layouts
Use POST /v2/layouts/add
instead.
1.4.0
Release date: 15.05.2024
New Features
- Support for Okta authentication.
- Implemented
"empty"
DataRequest
filter type for all filter types where applicable.Improvements & Bug Fixes
- Added
inRange
filters support for MongoDB.- Fixed preferences upsert.
1.3.0
Release date: 26.04.2024
New Features
- DB purge operation now happens at startup.
- Exposed extra Microsoft SQL Server options.
Improvements & Bug Fixes
- Fixed inconsistent group resolution between apps and Layouts in io.Manager.
- Fixed broken last updated timestamps in io.Manager leading to unnecessary database requests and hashing operations when configured with PostgreSQL or Microsoft SQL Server.
- Fixed summary endpoint on Microsoft SQL Server and PostgreSQL.
- DB purge interval is stopped when
server.stop()
is called.- Remove server-x token groups usage in sessions service.
1.2.0
Release date: 22.03.2024
New Features
- Added a configurable purge job for purging old audit logs, feedback and crashes in order to reduce database usage.
- Added
API_STORE_POSTGRESQL_NATIVE_PG_DRIVER
andAPI_STORE_MSSQL_DOMAIN
environment variables.Improvements & Bug Fixes
- Implemented ORFilters and excludeFields for PostgreSQL and Microsoft SQL Server.
- User groups defined in database are considered when using custom auth provider and the data store.
- Rebuilt the Data Request functionality for PostgreSQL and Microsoft SQL Server to use SQL parameters. Fixed various related bugs.
- Added migration for missing constraints in
layouts
andprefs
tables in PostgreSQL and Microsoft SQL Server.
1.1.1
Release date: 06.03.2024
Improvements & Bug Fixes
- When a user saves a shared Layout, a new private copy of that Layout is created. Previously, the shared Layout was transferred to the user that had saved it.
1.1.0
Release date: 24.02.2024
New Features
- Added support for
pg-native
driver.⚠️ Note that
pg-native
isn't a dependency of the@interopio/manager
package and you must install it separately in your project.Improvements & Bug Fixes
- Microsoft SQL Server support: fixed a bug where the
accessList
column of theapps
table wasn't written if empty.- Updated dependencies.
1.0.0
Release date: 17.01.2024
Breaking Changes
- Users can now be compared in a case-insensitive way. Added new a configuration property
username_case_sensitive
and a new environment variableAPI_USERNAME_CASE_SENSITIVE
that can be used to switch between case-sensitive and case-insensitive modes. Defaults to case-insensitive.- Removed status endpoint, because the
express-status-monitor
package is deprecated.Improvements & Bug Fixes
- Updated dependencies.
0.1
0.21.0
Release date: 15.11.2023
New Features
- Added ability to provide custom store implementation through configuration.
0.20.1
Release date: 20.10.2023
Improvements & Bug Fixes
- Updated dependencies.
0.20.0
Release date: 09.10.2023
New Features
- Added option for controlling audit logs.
Improvements & Bug Fixes
- Stopped recreating controllers on every request.
- Disabled auditing for opening sessions open and creating users.
0.19.2
Release date: 05.09.2023
Improvements & Bug Fixes
- Fixed updating a Layout without a Layout ID.
0.19.1
Release date: 14.07.2023
Improvements & Bug Fixes
- Moved several types from development dependencies to dependencies.
0.19.0
Release date: 14.07.2023
New Features
- Added support for Microsoft SQL Server databases.
0.18.0
Release date: 15.06.2023
New Features
- Added explicit Layouts support for PostgreSQL.
- Auth0 authentication now uses permissions.
Improvements & Bug Fixes
- Fixed rejecting hello request from io.Connect Browser.
0.17.1
Release date: 30.05.2023
Improvements & Bug Fixes
- Moved some of the libraries into the codebase for better control over the dependencies.
0.17.0
Release date: 22.05.2023
New Features
- Exposed APIs (e.g., for users, apps, Layouts and more) attached to the initialized
server
object.
0.16.0
Release date: 19.05.2023
New Features
- Added ability to set explicit Layouts for users.
0.15.2
Release date: 18.05.2023
Improvements & Bug Fixes
- Optimized fetching of user Layouts.
0.15.1
Release date: 11.05.2023
Improvements & Bug Fixes
- Exposed all options for Auth0 configuration.
0.15.0
Release date: 11.05.2023
New Features
- Restored Auth0 authentication support.
0.14.0
Release date: 11.04.2023
New Features
- Added an extra pool setting for PostgreSQL connections.
0.13.0
Release date: 31.03.2023
Improvements & Bug Fixes
- Updated to latest
@interopio/schemas
.
0.12.1
Release date: 16.03.2023
Improvements & Bug Fixes
- Updated dependencies.
0.12.0
Release date: 26.01.2023
New Features
- Allow a single default Layout entry in the database.
Improvements & Bug Fixes
- Prevented users from overwriting common Layouts.
0.11.0
Release date: 25.11.2022
New Features
- Added HTTPS support.
0.10.0
Release date: 28.10.2022
New Features
- Added support for PostgreSQL databases.
0.9.11
Release date: 12.10.2022
Improvements & Bug Fixes
- Added option to disable
express-status-monitor
.
0.9.10
Release date: 10.10.2022
Improvements & Bug Fixes
- Fixed always converting the port in the server configuration to a number. Now, if a string is passed, it's treated as a path that might be a named pipe.
0.9.9
Release date: 21.09.2022
New Features
- Added a
/status
endpoint usingexpress-status-monitor
.- Added a
/db
endpoint for database info.
0.9.8
Release date: 19.09.2022
Improvements & Bug Fixes
0.9.7
Release date: 19.09.2022
Improvements & Bug Fixes
- Removed sort memory limit.
0.9.6
Release date: 19.09.2022
Improvements & Bug Fixes
- Improved the shutdown process.
0.9.5
Release date: 07.09.2022
Improvements & Bug Fixes
- Improved Sentry monitoring routes.
0.9.4
Release date: 24.08.2022
New Features
- Added Sentry monitoring.
0.8.4
Release date: 07.06.2022
Improvements & Bug Fixes
- Updated to latest
@interopio/server-api
.
0.8.3
Release date: 07.06.2022
Improvements & Bug Fixes
- Hashed passwords (only used in Basic authentication).
- Updated dependencies.
0.8.2
Release date: 23.03.2022
Improvements & Bug Fixes
- Handled schema validator errors.
0.8.1
Release date: 23.03.2022
Improvements & Bug Fixes
- Fixed schema path.
0.8.0
Release date: 22.03.2022
New Features
- Added a
/schema
endpoint.
0.7.0
Release date: 21.03.2022
New Features
- Added a flow for Basic authentication.
- Added a
/whoami
endpoint.
0.6.0
Release date: 17.03.2022
New Features
- Added a default route.
- Added a stop route that is registered only if an environment variable is present in the configuration.
0.5.0
Release date: 13.03.2022
New Features
- Added a
/capabilities
endpoint for exposing the features of Groups.
0.4.1
Release date: 13.03.2022
Improvements & Bug Fixes
- Included the tests as pre-publish step.
0.4.0
Release date: 13.03.2022
New Features
- Added the option to provide a custom Groups service.