# o isSuppressSchemaHtmlOutsideSql: (NotRequired - Default false)
# o isSuppressSchemaHtmlProcedure: (NotRequired - Default false)
# o historyHtmlFileName: (NotRequired - Default 'history-[project-name].html')
# o isCheckColumnDefOrderDiff: (NotRequired - Default false)
# o isCheckDbCommentDiff: (NotRequired - Default false)
# o isCheckProcedureDiff: (NotRequired - Default false)

                display = ParameterDisplay.PROMPT,
                allowEmpty = true,
            )
        }

        cleanup {
            history(days = 180)
        }

        this.init()
    }
}

class PublishFinalRelease(
    branch: VersionedSettingsBranch,
) : PublishRelease(
        promotedBranch = branch.branchName,

### Summary { #summary }

I used to say I didn't like history that much... and look at me now giving "tech history" lessons. 😅

 * See https://www.jetbrains.com/help/teamcity/teamcity-data-clean-up.html#Clean-up+Rules
 *
 * @param historyDays days number of days to store build history .
 * @param artifactsDays number of days to store artifacts. In the stored history, artifacts older than this number will be cleaned up.
 * @param artifactPatterns patterns for artifacts clean-up. If not specified, all artifacts will be removed.
 */

/**
 * The assist for login handling in the Fess application.
 * This class extends TypicalLoginAssist to provide Fess-specific login functionality
 * including user authentication, permission checking, and login history management.
 *
 */
public class FessLoginAssist extends TypicalLoginAssist<String, FessUserBean, FessUser> // #change_it also UserBean
        implements PrimaryLoginManager {

    /**
     * Default constructor.

 * which provides a command-line interface for executing Maven commands and
 * managing build environments.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Interactive command-line interface</li>
 *   <li>Command history and completion</li>
 *   <li>Built-in shell commands</li>
 *   <li>Project navigation and management</li>
 * </ul>
 *
 * @see org.apache.maven.api.cli.Tools#MVNSHELL_CMD

		// Config KV history operations.
		if enableConfigOps {
			adminRouter.Methods(http.MethodGet).Path(adminVersion+"/list-config-history-kv").HandlerFunc(adminMiddleware(adminAPI.ListConfigHistoryKVHandler, traceAllFlag)).Queries("count", "{count:[0-9]+}")

    - 'R8/Proguard': features/r8_proguard.md
  - 'Recipes': recipes.md
  - 'Security':
    - 'Security': security/security.md
    - 'Providers': security/security_providers.md
    - 'Configuration History': security/tls_configuration_history.md
  - 'Works with OkHttp': works_with_okhttp.md
  - 'API': 5.x/okhttp/okhttp3/
  - 'Change Logs':
    - 'Change Log': changelogs/changelog.md

the defaults for the Go toolchain used to build the program,
amended to match the Go version listed in `go.mod`,
and then overridden by explicit `//go:debug` lines in the program.

The [GODEBUG History](#history) gives the exact defaults for each Go toolchain version.
For example, Go 1.21 introduces the `panicnil` setting,
controlling whether `panic(nil)` is allowed;
it defaults to `panicnil=0`, making `panic(nil)` a run-time error.

    //                                                                      ==============

    // GET /api/admin/joblog/logs
    /**
     * Returns list of job logs.
     * Supports filtering and pagination for job execution history.
     *
     * @param body search parameters for filtering and pagination
     * @return JSON response containing job logs list with pagination info
     */
    @Execute