- Upgrade default Camel JBang version from 4.18.0 to 4.20.0
- fix: allow user to overwrite default run arguments
- display
*openapi.ymlfiles in OpenAPI view by default - fix JSON OpenAPI files detection and file validation
- removed file extension restrictions from API URL imports, enabling greater flexibility with various URL formats.
- Upgrade default Camel JBang version from 4.16.0 to 4.18.0
- export Maven projects with OpenShift deployment configurations using Camel Kubernetes plugin
- export Maven projects with predefined VS Code launch configurations for easy deployment to OpenShift
- Add
Testssection into Kaoto view- list existing Citrus tests in a current workspace
- create a new Citrus Test file button
- run single test or all tests in a folder
- test files regex can be configured through settings
- Upgrade to Kaoto 2.10.0
- Add
OpenAPIinto Kaoto view- list existing OpenAPI specification files (
*openapi.jsonor*openapi.yaml) - import OpenAPI into Kaoto - file, URI or Apicurio Registry
- list existing OpenAPI specification files (
- Rework Integrations section of Kaoto view to bring tree-like structure
- Add buttons
Run: FolderandRun: Workspaceinto Integrations section of Kaoto view - User setting allowing specify a list of local kamelet directories used for integrations run
- Upgrade to Kaoto 2.9.0
- Add button
Export FolderandExport: Workspaceinto Integrations section of Kaoto view
- Upgrade to Kaoto 2.8.3
- Allow to update Maven dependencies on not fully configured route
- Use Node 22 instead of Node 20
- Fix link pointing to documentation to generate custom catalog
- show
What's Newrelease page after each extension upgrade (only for first startup) - Upgrade default Camel JBang version from 4.14.0 to 4.16.0
- Allow manual Camel dependencies update in pom.xml
- Add
Kaoto first stepsextension walkthrough
- Upgrade to Kaoto 2.7.1
- /!\ BREAKING CHANGE: if using a specific Kaoto Catalog, it must be regenerated with newer Kaoto otherwise the editor won't open.
- Support for switching themes independently of VS Code theme
- The Kaoto editor must closed/reopened to have theme applied
- Upgrade default Camel JBang version from 4.11.0 to 4.14.0
- Note that due to regression CAMEL-22131 in Camel JBang 4.12, the project creation on Windows doesn't include the Maven wrapper with 4.12.x Camel Jbang version.
- Drag-and-Drop functionality on Kaoto canvas now enabled by default
- BREAKING CHANGE: Camel JBang user settings have now different IDs, so for those who are using local workspace VS Code settings they need to be updated to new values
- Update Camel dependencies in pom.xml for Maven projects automatically on editor save when step into Kaoto canvas is added or replaced
- can be disabled via UI setting (enabled by default)
- allowed only for Camel JBang 4.14+
- Upgrade to Kaoto 2.6.0
- Add recommended extensions pop up notification
Breaking:Remove legacy support for Kaoto v1 file patterns (*.kaoto.yaml,*.kaoto.yml)Breaking:Bump minimal VS Code version from 1.74.0 to 1.95.0- Potential breakage: when using a Camel Jbang version strictly prior to 4.11, the parameter
--disable-automust be removed from the settingKubernetes Run Parameters - Upgrade to Kaoto 2.5.0
- Add Kaoto view container with initial Help & Feedback view
- Improve toggle source code (open/close camel file in a side textual editor) using one button
- Add Integrations view into Kaoto view container
- Add
New File...button intoKaoto: Integrationsview - Add automatically Apache Camel into JBang Trusted Sources
- add welcome content into Kaoto: Integrations view
- show Open Folder when there is no workspace
- show New Camel File if no Camel related file is found in workspace (when Integrations view is empty)
- send events into Red hat Telemetry for Kaoto extension commands
- Add
Exportinline button into Kaoto: Integrations view - Add
Runinline button into Kaoto: Integrations view - Add
Deployinline button into Kaoto: Integrations view - Add support for XML files -
*.camel.xmlfiles are automatically opened in Kaoto editor- Kaoto: Integrations view
- create new Camel Route using XML DSL
- list XML files with route elements
- Kaoto: Integrations view
- Add
Deploymentsview into Kaoto view container which displays all local running integrations - Add
StopandFollow Logsaction buttons into Deployments view - Add
Start/Stop/Suspend/Resumeaction button onroutelevel within Deployments view - Support for Dark theme
- The Kaoto editor must closed/reopened to have theme applied
- The High Contrast Dark Theme is not supported
- Fix Kaoto Datamapper editor on Windows (issue when attaching an xsd)
- Upgrade to Kaoto 2.4.0
- Add the possibility to select how to show the Step toolbar (onHover or onSelection)
- Add the possibility to enable drag & drop experimental feature
- Introduced a
Kaotooutput channel. It is initially used to log message of exceptions. - Upgrade to Kaoto 2.3.0
- Start attempt to have VS Code Kaoto version number aligned with version of Kaoto that is embedded
- Enable
nodeLabelsetting to configure the node label used in the Kaoto editor - Upgrade Kaoto 2.2.0
- Provide command and quick action
Open Camel file with textual editor on the sidewhen Kaoto editor is active - Provide shortcut
Ctrl+k vto open textual editor to the side when kaoto editor is active - Fix rendering in vscode.dev
- Fix commands in vscode.dev
- Update project homepage in the marketplace to kaoto.io
- Setting to provide custom set of Catalog used by the Kaoto editor
- Upgrade Kaoto 2.1.0
- Update Red Hat telemetry dependency to reduce number of event sent (startup information will be sent one time per day per user)
- Remove
previewflag
- Update animated image in readme
- Upgrade from Kaoto 2 preview release 2.0.0-TP3 to 2.0.0
- Upgrade from Kaoto 2 preview release 2.0.0-TP2 to 2.0.0-TP3
- Open Kaoto editor by default for
*.pipe.(yaml|yml)and*-pipe.(yaml|yml)files
- Upgrade from Kaoto 2 preview release 2.0.0-TP1.2 to 2.0.0-TP2
- Fix Kaoto editor in vscode.dev web environment
- Upgrade from Kaoto 2 preview release 2.0.0-TP1 to 2.0.0-TP1.2
- Use Kaoto 2 preview release (technically kaoto-next 2.0.0-TP1) instead of Kaoto UI + Kaoto backend
- Remove kaoto backend v1: reduced size of bundle and no more requirements on architecture
- Open Kaoto editor by default for
*.kamelet.(yaml|yml)files
- Change default port of embedded Kaoto backend from
8081to8097
- Keep
Kaoto backendoutput log available when Kaoto backend native executable cannot be launched. It allows to have more information what can be the issue. - Upgrade embedded Kaoto UI to 0.7.6 and backend to 0.7.6
- Open Kaoto editor by default for
*.camel.(yaml|yml)files - Provide entry in contextual menu to open
*.(yaml|yml)files with Kaoto editor - Avoid wipeout of content on restart with opened editors #144
- Technical version to be able to push on Marketplace
- Initial version: Open a Kaoto file, edit it and save it inside VS Code.