Remove old "introduced in" notices

docs/configuration/miscellaneous.md

@@ -108,8 +108,6 @@ By default, NetBox will prevent the creation of duplicate prefixes and IP addres
 
 ## EVENTS_PIPELINE
 
-!!! info "This parameter was introduced in NetBox v4.2."
-
 Default: `['extras.events.process_event_queue',]`
 
 NetBox will call dotted paths to the functions listed here for events (create, update, delete) on models as well as when custom EventRules are fired.

docs/configuration/required-parameters.md

@@ -34,8 +34,6 @@ See the [`DATABASES`](#databases) configuration below for usage.
 
 ## DATABASES
 
-!!! info "This parameter was introduced in NetBox v4.3."
-
 NetBox requires access to a PostgreSQL 14 or later database service to store data. This service can run locally on the NetBox server or on a remote system. Databases are defined as named dictionaries:
 
 ```python

docs/configuration/system.md

@@ -14,8 +14,6 @@ BASE_PATH = 'netbox/'
 
 ## DATABASE_ROUTERS
 
-!!! info "This parameter was introduced in NetBox v4.3."
-
 Default: `[]` (empty list)
 
 An iterable of [database routers](https://docs.djangoproject.com/en/stable/topics/db/multi-db/) to use for automatically selecting the appropriate database(s) for a query. This is useful only when [multiple databases](./required-parameters.md#databases) have been configured.
@@ -186,8 +184,6 @@ The file path to the location where media files (such as image attachments) are
 
 ## PROXY_ROUTERS
 
-!!! info "This parameter was introduced in NetBox v4.3."
-
 Default: `["utilities.proxy.DefaultProxyRouter"]`
 
 A list of Python classes responsible for determining which proxy server(s) to use for outbound HTTP requests. Each item in the list can be the class itself or the dotted path to the class.

docs/models/circuits/circuit.md

@@ -38,8 +38,6 @@ The operational status of the circuit. By default, the following statuses are av
 
 ### Distance
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The distance between the circuit's two endpoints, including a unit designation (e.g. 100 meters or 25 feet).
 
 ### Description

docs/models/circuits/virtualcircuit.md

@@ -1,7 +1,5 @@
 # Virtual Circuits
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 A virtual circuit can connect two or more interfaces atop a set of decoupled physical connections. For example, it's very common to form a virtual connection between two virtual interfaces, each of which is bound to a physical interface on its respective device and physically connected to a [provider network](./providernetwork.md) via an independent [physical circuit](./circuit.md).
 
 ## Fields

docs/models/circuits/virtualcircuittermination.md

@@ -1,7 +1,5 @@
 # Virtual Circuit Terminations
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 This model represents the connection of a virtual [interface](../dcim/interface.md) to a [virtual circuit](./virtualcircuit.md).
 
 ## Fields

docs/models/core/datasource.md

@@ -46,8 +46,6 @@ A set of rules (one per line) identifying filenames to ignore during synchroniza
 
 ### Sync Interval
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The interval at which the data source should automatically synchronize. If not set, the data source must be synchronized manually.
 
 ### Last Synced

docs/models/dcim/devicerole.md

@@ -6,8 +6,6 @@ Devices can be organized by functional roles, which are fully customizable by th
 
 ### Parent
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The parent role of which this role is a child (optional).
 
 ### Name

docs/models/dcim/interface.md

@@ -126,8 +126,6 @@ The tagged VLANs which are configured to be carried by this interface. Valid onl
 
 ### Q-in-Q SVLAN
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The assigned service VLAN (for Q-in-Q/802.1ad interfaces).
 
 ### Wireless Role
@@ -155,6 +153,4 @@ The [wireless LANs](../wireless/wirelesslan.md) for which this interface carries
 
 ### VLAN Translation Policy
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The [VLAN translation policy](../ipam/vlantranslationpolicy.md) that applies to this interface (optional).

docs/models/dcim/inventoryitem.md

@@ -30,8 +30,6 @@ An alternative physical label identifying the inventory item.
 
 ### Status
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The inventory item's operational status.
 
 ### Role

docs/models/dcim/macaddress.md

@@ -1,7 +1,5 @@
 # MAC Addresses
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 A MAC address object in NetBox comprises a single Ethernet link layer address, and represents a MAC address as reported by or assigned to a network interface. MAC addresses can be assigned to [device](../dcim/device.md) and [virtual machine](../virtualization/virtualmachine.md) interfaces. A MAC address can be specified as the primary MAC address for a given device or VM interface.
 
 Most interfaces have only a single MAC address, hard-coded at the factory. However, on some devices (particularly virtual interfaces) it is possible to assign additional MAC addresses or change existing ones. For this reason NetBox allows multiple MACAddress objects to be assigned to a single interface.

docs/models/dcim/moduletypeprofile.md

@@ -1,7 +1,5 @@
 # Module Type Profiles
 
-!!! info "This model was introduced in NetBox v4.3."
-
 Each [module type](./moduletype.md) may optionally be assigned a profile according to its classification. A profile can extend module types with user-configured attributes. For example, you might want to specify the input current and voltage of a power supply, or the clock speed and number of cores for a processor.
 
 Module type attributes are managed via the configuration of a [JSON schema](https://json-schema.org/) on the profile. For example, the following schema introduces three module type attributes, two of which are designated as required attributes.

docs/models/dcim/poweroutlet.md

@@ -40,12 +40,8 @@ The operational status of the power outlet. By default, the following statuses a
 !!! tip "Custom power outlet statuses"
     Additional power outlet statuses may be defined by setting `PowerOutlet.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.
 
-!!! info "This field was introduced in NetBox v4.3."
-
 ### Color
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The power outlet's color (optional).
 
 ### Power Port

docs/models/dcim/racktype.md

@@ -42,8 +42,6 @@ The number of the numerically lowest unit in the rack. This value defaults to on
 
 The external width, height and depth of the rack can be tracked to aid in floorplan calculations. These measurements must be designated in either millimeters or inches.
 
-!!! info "The `outer_height` field was introduced in NetBox v4.3."
-
 ### Mounting Depth
 
 The maximum depth of a mounted device that the rack can accommodate, in millimeters. For four-post frames or cabinets, this is the horizontal distance between the front and rear vertical rails. (Note that this measurement does _not_ include space between the rails and the cabinet doors.)

docs/models/extras/configtemplate.md

@@ -34,24 +34,15 @@ The `undefined` and `finalize` Jinja environment parameters, which must referenc
 
 ### MIME Type
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The MIME type to indicate in the response when rendering the configuration template (optional). Defaults to `text/plain`.
 
 ### File Name
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The file name to give to the rendered export file (optional).
 
 ### File Extension
 
-!!! info "This field was introduced in NetBox v4.3."
-
 The file extension to append to the file name in the response (optional).
 
 ### As Attachment
-
-!!! info "This field was introduced in NetBox v4.3."
-
 If selected, the rendered content will be returned as a file attachment, rather than displayed directly in-browser (where supported).

docs/models/extras/exporttemplate.md

@@ -22,8 +22,6 @@ Jinja2 template code for rendering the exported data.
 
 ### Environment Parameters
 
-!!! info "This field was introduced in NetBox v4.3."
-
 A dictionary of any additional parameters to pass when instantiating the [Jinja2 environment](https://jinja.palletsprojects.com/en/3.1.x/api/#jinja2.Environment). Jinja2 supports various optional parameters which can be used to modify its default behavior.
 
 The `undefined` and `finalize` Jinja environment parameters, which must reference a Python class or function, can define a dotted path to the desired resource. For example:

docs/models/extras/tag.md

@@ -20,8 +20,6 @@ The color to use when displaying the tag in the NetBox UI.
 
 A numeric weight employed to influence the ordering of tags. Tags with a lower weight will be listed before those with higher weights. Values must be within the range **0** to **32767**.
 
-!!! info "This field was introduced in NetBox v4.3."
-
 ### Object Types
 
 The assignment of a tag may be limited to a prescribed set of objects. For example, it may be desirable to limit the application of a specific tag to only devices and virtual machines.

docs/models/ipam/vlan.md

@@ -32,12 +32,8 @@ The [VLAN group](./vlangroup.md) or [site](../dcim/site.md) to which the VLAN is
 
 ### Q-in-Q Role
 
-!!! info "This field was introduced in NetBox v4.2."
-
 For VLANs which comprise a Q-in-Q/IEEE 802.1ad topology, this field indicates whether the VLAN is treated as a service or customer VLAN.
 
 ### Q-in-Q Service VLAN
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The designated parent service VLAN for a Q-in-Q customer VLAN. This may be set only for Q-in-Q custom VLANs.

docs/models/ipam/vlantranslationpolicy.md

@@ -1,7 +1,5 @@
 # VLAN Translation Policies
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 VLAN translation is a feature that consists of VLAN translation policies and [VLAN translation rules](./vlantranslationrule.md). Many rules can belong to a policy, and each rule defines a mapping of a local to remote VLAN ID (VID). A policy can then be assigned to an [Interface](../dcim/interface.md) or [VMInterface](../virtualization/vminterface.md), and all VLAN translation rules associated with that policy will be visible in the interface details.
 
 There are uniqueness constraints on `(policy, local_vid)` and on `(policy, remote_vid)` in the `VLANTranslationRule` model. Thus, you cannot have multiple rules linked to the same policy that have the same local VID or the same remote VID. A set of policies and rules might look like this:

docs/models/ipam/vlantranslationrule.md

@@ -1,7 +1,5 @@
 # VLAN Translation Rules
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 A VLAN translation rule represents a one-to-one mapping of a local VLAN ID (VID) to a remote VID. Many rules can belong to a single policy.
 
 See [VLAN translation policies](./vlantranslationpolicy.md) for an overview of the VLAN Translation feature.

docs/models/virtualization/vminterface.md

@@ -59,8 +59,6 @@ The tagged VLANs which are configured to be carried by this interface. Valid onl
 
 ### Q-in-Q SVLAN
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The assigned service VLAN (for Q-in-Q/802.1ad interfaces).
 
 ### VRF
@@ -69,6 +67,4 @@ The [virtual routing and forwarding](../ipam/vrf.md) instance to which this inte
 
 ### VLAN Translation Policy
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The [VLAN translation policy](../ipam/vlantranslationpolicy.md) that applies to this interface (optional).

docs/models/vpn/l2vpn.md

@@ -44,8 +44,6 @@ The operational status of the L2VPN. By default, the following statuses are avai
 !!! tip "Custom L2VPN statuses"
     Additional L2VPN statuses may be defined by setting `L2VPN.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.
 
-!!! info "This field was introduced in NetBox v4.3."
-
 ### Identifier
 
 An optional numeric identifier. This can be used to track a pseudowire ID, for example.

docs/models/wireless/wirelesslan.md

@@ -46,6 +46,4 @@ The security key configured on each client to grant access to the secured wirele
 
 ### Scope
 
-!!! info "This field was introduced in NetBox v4.2."
-
 The [region](../dcim/region.md), [site](../dcim/site.md), [site group](../dcim/sitegroup.md) or [location](../dcim/location.md) with which this wireless LAN is associated.

docs/plugins/development/background-jobs.md

@@ -89,8 +89,6 @@ class MyModel(NetBoxModel):
 
 ### System Jobs
 
-!!! info "This feature was introduced in NetBox v4.2."
-
 Some plugins may implement background jobs that are decoupled from the request/response cycle. Typical use cases would be housekeeping tasks or synchronization jobs. These can be registered as _system jobs_ using the `system_job()` decorator. The job interval must be passed as an integer (in minutes) when registering a system job. System jobs are scheduled automatically when the RQ worker (`manage.py rqworker`) is run.
 
 #### Example

docs/plugins/development/models.md

@@ -119,8 +119,6 @@ For more information about database migrations, see the [Django documentation](h
 
 ::: netbox.models.features.ContactsMixin
 
-!!! info "Plugin support for ContactsMixin was introduced in NetBox v4.3."
-
 ::: netbox.models.features.CustomLinksMixin
 
 ::: netbox.models.features.CustomFieldsMixin