[main] Update package versions#23
Closed
aholstrup1 wants to merge 10 commits into
Closed
Conversation
## Preview Note that when using the preview version of AL-Go for GitHub, you need to Update your AL-Go system files, as soon as possible when told to do so. ### Issues Issue #446 Wrong NewLine character in Release Notes Issue #453 DeliverToStorage - override fails reading secrets Issue #434 Use gh auth token to get authentication token instead of gh auth status Issue #501 The Create New App action will now use 22.0.0.0 as default application reference and include NoImplicitwith feature. ### New behavior The following workflows: - Create New App - Create New Test App - Create New Performance Test App - Increment Version Number - Add Existing App - Create Online Development Environment All these actions now uses the selected branch in the **Run workflow** dialog as the target for the Pull Request or Direct COMMIT. ### New Settings - `UseCompilerFolder`: Setting useCompilerFolder to true causes your pipelines to use containerless compiling. Unless you also set `doNotPublishApps` to true, setting useCompilerFolder to true won't give you any performance advantage, since AL-Go for GitHub will still need to create a container in order to publish and test the apps. In the future, publishing and testing will be split from building and there will be other options for getting an instance of Business Central for publishing and testing. - `vsixFile`: vsixFile should be a direct download URL to the version of the AL Language extension you want to use for building the project or repo. By default, AL-Go will use the AL Language extension that comes with the Business Central Artifacts. ### New Actions - **DetermineArtifactUrl** is used to determine which artifacts to use for building a project in CI/CD, PullRequestHandler, Current, NextMinor and NextMajor workflows. ### License File With the changes to the CRONUS license in Business Central version 22, that license can in most cases be used as a developer license for AppSource Apps and it is no longer mandatory to specify a license file in AppSource App repositories. Obviously, if you build and test your app for Business Central versions prior to 21, it will fail if you don't specify a licenseFileUrl secret. --------- Co-authored-by: aholstrup1 <aholstrup1@users.noreply.github.com>
Co-authored-by: aholstrup1 <aholstrup1@users.noreply.github.com>
auto-merge was automatically disabled
May 25, 2023 14:19
Pull request was closed
aholstrup1
added a commit
that referenced
this pull request
May 26, 2023
onbuyuka
added a commit
that referenced
this pull request
Jun 2, 2026
Implements the review feedback on the MCP configuration feature plus a follow-up quality pass. Feedback: - Default field is read-only on the card; Set as Default / Clear Default actions (promoted) are back on the configuration list. - Renamed AL Query Tools -> Data Query Tools (Preview) across the code: enum value, handler codeunit (MCP Data Query Tools Feature), facade/impl procedures, the mock activation field, and tests. The mock system-tool IDs compile_al_query / run_al_query are kept. - Select APIs opens one lookup over both API pages and API queries (new temp table "MCP API Object Buffer" + page "MCP API Object Lookup", populated by MCPConfigImplementation.LookupAPIObjects). The per-row Object Id lookup shares the same path. - Configuration list shows read-only API Tools / Data Query Tools status columns instead of Dynamic Tool Mode / Discover Read-Only Objects. - Permissions: registered the recently-added tables and the new buffer in "MCP - Objects" and granted tabledata on the persistent MCP Feature Activation (R/IMD) - these were missing and broke the feature for non-SUPER users. Quality pass: - Removed the now-orphaned per-type lookups (LookupAPIPageTools / LookupAPIQueryTools, pages "MCP API Config Tool Lookup" / "MCP Query Config Tool Lookup", their test-library wrappers and two tests) in favour of the unified lookup; one TestLookupAPIObjects smoke test replaces them. - "MCP API Object Buffer" declared TableType = Temporary (matching sibling buffers); temp-record variable naming aligned to the LinterCop convention (locals Temp-prefixed, parameters not). Design doc updated throughout (D33-D34, Appendix C #23-24, Appendix E, the AL Query -> Data Query naming note, lookup page renumber 8360 -> 8376). AB#631012 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.