Version number management method and device, equipment and storage medium

Abstract

This application provides a version number management method, apparatus, device, and storage medium, belonging to the field of computer technology. The method includes: receiving selection information sent by a terminal, and confirming an updated major version number based on the selection information, wherein the selection information represents version information of the major version number obtained by the terminal according to preset selection rules; receiving update content of the major version number sent by the terminal, and creating a preliminary version number, wherein the preliminary version number represents the update content of the major version number; sending an update notification of the major version number to an authentication terminal, so that the authentication terminal executes an authentication process and obtains authentication information confirming the update content; receiving the authentication information confirming the update content sent by the authentication terminal, and changing the preliminary version number to the updated major version number based on the authentication information and the update content. This application embodiment can achieve unified version number updates to avoid version number conflicts.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a version number management method, apparatus, device and storage medium. Background Technology

[0002] In system or software development, systems are typically divided into multiple business function components, each developed separately. During the iterative updates of these components, a version number is usually assigned to each component to facilitate understanding and tracking of its status. Version numbers are a means of defining functionality at a specific time, making version number management extremely important. However, current version number updates are not standardized, leading to potential conflicts. For example, if a business function component is used in different integrated components, the lack of standardized version number updates can result in different version numbers for the same component at different times, causing version number conflicts. Therefore, avoiding version number conflicts has become a pressing technical problem. Summary of the Invention

[0003] The main objective of this application is to provide a version number management method, apparatus, device, and storage medium, which aims to achieve unified version number updates to avoid version number conflicts.

[0004] To achieve the above objectives, a first aspect of this application proposes a version number management method, applied to a system, the method comprising:

[0005] The terminal receives selection information and confirms the updated major version number based on the selection information, wherein the selection information represents the version information of the major version number obtained by the terminal according to a preset selection rule;

[0006] The system receives the update content of the major version number sent by the terminal and creates a preliminary version number, wherein the preliminary version number represents the update content of the major version number.

[0007] The update notification of the major version number is sent to the authentication terminal so that the authentication terminal can execute the authentication process and obtain authentication information confirming the update content;

[0008] The system receives the authentication information sent by the authentication terminal confirming the updated content, and changes the preliminary version number to the updated major version number based on the authentication information and the updated content.

[0009] In some embodiments, confirming the updated major version number based on the selection information includes:

[0010] A reminder message is sent to the terminal based on the selected information;

[0011] The terminal receives a confirmation message sent based on the reminder message, wherein the confirmation message indicates confirmation of updating the major version number.

[0012] In some embodiments, receiving the update content of the major version number sent by the terminal includes:

[0013] The terminal sends an update message for the major version number, wherein the update message includes the version number of the major version number.

[0014] The updated content is stored in a log file, and the storage result is sent to the terminal.

[0015] In some embodiments, sending the update notification of the major version number to the authentication terminal, so that the authentication terminal performs the authentication process and obtains authentication information confirming the update content, includes:

[0016] Obtain a preset list to find the authentication terminal in the list that corresponds to the main version number;

[0017] Send the update notification for the major version number to the corresponding authentication terminal;

[0018] The authentication information sent by the authentication terminal is received, wherein the authentication information is obtained by the authentication terminal executing a preset second script to obtain the updated content and verify the updated content.

[0019] In some embodiments, before receiving selection information from the receiving terminal and confirming the updated major version number based on the selection information, the method further includes:

[0020] Execute a preset first script to obtain the selection rules, wherein the selection rules characterize the update method of the major version number.

[0021] To achieve the above objectives, a second aspect of this application proposes a version number management method applied to a terminal, the method comprising:

[0022] According to preset selection rules, the terminal displays an option to update the major version number, and the selection information of the major version number is determined according to the user's selection operation of the option to update the major version number, wherein the selection information represents the version information of the major version number obtained by the terminal according to the preset selection rules;

[0023] Send the selection information of the major version number to the system.

[0024] Obtain the update content of the major version number and send the update content of the major version number to the system.

[0025] In some embodiments, the method further includes:

[0026] Receive the reminder information sent by the system terminal based on the selection information;

[0027] A confirmation message is sent to the system based on the reminder message, wherein the confirmation message indicates confirmation of updating the major version number.

[0028] To achieve the above objectives, a third aspect of this application provides a version number management device, comprising:

[0029] The option operation module is used to display the option to update the main version number on the terminal according to the preset selection rules, and to determine the selection information of the main version number according to the user's selection operation of the option to update the main version number, wherein the selection information represents the version information of the main version number obtained by the terminal according to the preset selection rules.

[0030] The selection sending module is used to send the selection information of the main version number to the system.

[0031] The content sending module is used to obtain the update content of the major version number and send the update content of the major version number to the system terminal;

[0032] The update selection module is used to receive the selection information sent by the terminal and confirm the major version number to be updated based on the selection information.

[0033] A creation module is used to receive the update content of the major version number sent by the terminal and create a preliminary version number, wherein the preliminary version number represents the update content of the major version number;

[0034] The notification authentication module is used to send the update notification of the major version number to the authentication terminal, so that the authentication terminal can execute the authentication process and obtain authentication information confirming the update content;

[0035] The version update module is used to receive the authentication information sent by the authentication terminal confirming the update content, and change the preliminary version number to the updated major version number according to the authentication information and the update content.

[0036] To achieve the above objectives, a fourth aspect of this application provides an electronic device, the electronic device including a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for implementing communication between the processor and the memory, wherein the program, when executed by the processor, implements the methods described in the first and second aspects above.

[0037] To achieve the above objectives, a fifth aspect of the present application provides a storage medium, which is a computer-readable storage medium for computer-readable storage, wherein the storage medium stores one or more programs that can be executed by one or more processors to implement the methods described in the first and second aspects above.

[0038] The version number management method, apparatus, device, and storage medium proposed in this application firstly involve the system receiving selection information sent by the terminal and confirming the updated major version number based on the selection information. The selection information represents the version information of the major version number obtained by the terminal according to preset selection rules. Secondly, the system receives the update content of the major version number sent by the terminal and creates a preliminary version number, where the preliminary version number represents the update content of the major version number. Then, the system sends an update notification of the major version number to the authentication end, enabling the authentication end to execute the authentication process and obtain authentication information confirming the update content. Finally, the system receives the authentication information confirming the update content sent by the authentication end and, based on the authentication information and the update content, changes the preliminary version number to the updated major version number. In this method, when the major version number needs to be updated, the terminal sends the selection information for updating the major version number to the system and confirms it. The terminal then sends the updated major version number to the system. After the system completes the authentication process through the authentication terminal, it updates the major version number. By streamlining the process on the system side, the major version number can be updated uniformly. Furthermore, because of the added authentication process, the major version number will not be changed arbitrarily, thus avoiding the problem of conflicting major version numbers at the same time. Attached Figure Description

[0039] Figure 1 This is a flowchart of the version number management method provided in the embodiments of this application;

[0040] Figure 2 yes Figure 1 The flowchart of step S100 in the middle;

[0041] Figure 3 yes Figure 1 The flowchart of step S110 in the middle;

[0042] Figure 4 yes Figure 1 The flowchart of step S120 in the middle;

[0043] Figure 5 yes Figure 1 Another flowchart of the version number management method in the document;

[0044] Figure 6 This is another flowchart of the version number management method provided in the embodiments of this application;

[0045] Figure 7 yes Figure 6 Another flowchart of the version number management method in the document;

[0046] Figure 8 This is a schematic diagram of the version number management device provided in the embodiments of this application;

[0047] Figure 9 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0049] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0050] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0051] First, let's analyze some of the terms used in this application:

[0052] iOS: Mobile Operating System.

[0053] Python: A computer programming language.

[0054] Semantic versioning: Semantic versioning typically consists of three decimal digits separated by a period: major version number, minor version number, and fix number. During the software development cycle, version numbers increment over time. This means that for two versions of the same software, the major version number of the later release will never be less than the major version number of the earlier release. If the major version numbers are the same, the minor version number of the later release will never be less than the minor version number of the earlier release. If the minor version numbers are also the same, the fix number of the later release will always be larger.

[0055] Currently, in iOS application development, an application is typically developed collaboratively by multiple teams, each independently developing various functional modules. Each team requires multiple business function components to assemble these modules, and each business function component has its own version number. Version numbers are a means of defining functionality at a specific timeframe; therefore, version number management is extremely important. In related technologies, it's possible for two teams to depend on the same business function component, but the version number used by the two teams may differ. For example, if component A and component B both integrate component C, and component A also integrates component B, and if the version of component C integrated in A is 0.1.1, while the version of component C in component B is 0.2.1, a conflict arises. Therefore, providing a version number management method to avoid version number conflicts has become a pressing technical problem.

[0056] Based on this, embodiments of this application provide a version number management method, apparatus, electronic device, and storage medium, aiming to achieve unified version number updates to avoid version number conflicts.

[0057] The version number management method, apparatus, electronic device, and storage medium provided in this application are specifically described through the following embodiments. First, the version number management method in this application is described.

[0058] The version number management method provided in this application relates to the field of computer technology. This method can be applied to a terminal, a system, or software running on either a terminal or a system. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the system can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application of the version number management method, but is not limited to the above forms.

[0059] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0060] Figure 1 This is an optional flowchart of the version number management method provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S100 to S130.

[0061] Step S100: Receive selection information sent by the terminal and confirm the updated major version number according to the selection information, wherein the selection information represents the version information of the major version number obtained by the terminal according to the preset selection rules;

[0062] Step S110: Receive the update content of the major version number sent by the terminal and create a preliminary version number, wherein the preliminary version number represents the update content of the major version number;

[0063] Step S120: Send the update notification of the main version number to the authentication terminal so that the authentication terminal can execute the authentication process and obtain authentication information confirming the update content.

[0064] Step S130: Receive authentication information from the authentication terminal confirming the updated content, and change the preliminary version number to the updated major version number based on the authentication information and the updated content.

[0065] In steps S110 to S130 of this embodiment, firstly, the system receives selection information sent by the terminal and confirms the updated major version number based on the selection information, wherein the selection information represents the version information of the major version number obtained by the terminal according to a preset selection rule; secondly, the system receives the update content of the major version number sent by the terminal and creates a preliminary version number, wherein the preliminary version number represents the update content of the major version number; then, the system sends the update notification of the major version number to the authentication end so that the authentication end can execute the authentication process and obtain authentication information confirming the update content; finally, the system receives the authentication information confirming the update content sent by the authentication end and changes the preliminary version number to the updated major version number based on the authentication information and the update content. In this method, when the major version number needs to be updated, the terminal sends the selection information for updating the major version number to the system and confirms it. The terminal then sends the updated major version number to the system. After the system completes the authentication process through the authentication terminal, it updates the major version number. By streamlining the process on the system side, the major version number can be updated uniformly. Furthermore, because of the added authentication process, the major version number will not be changed arbitrarily, thus avoiding the problem of conflicting major version numbers at the same time.

[0066] In some embodiments, semantic version numbers are used. During the update process, there are different standard interpretations of the major version number, minor version number, and patch number, leading to inconsistencies between the updated version number and the expected version number. By executing steps S110 to S130, version number updates can be uniformly authenticated, achieving a unified standard interpretation.

[0067] Please see Figure 2 In some embodiments, confirming the updated major version number based on the selection information in step S100 may include, but is not limited to, steps S101 to S102:

[0068] Step S101: Send a reminder message to the terminal according to the selected information;

[0069] Step S102: Receive confirmation information sent by the receiving terminal based on the reminder information, wherein the confirmation information indicates confirmation of updating the major version number.

[0070] In step S101 of some embodiments, the selection information is obtained by the user inputting selection content on the terminal, and the selection content may be selecting to update the major version number; the reminder information is sent by the system according to the terminal's selection, and the reminder information may be whether to confirm updating the major version number.

[0071] In step S102 of some embodiments, after receiving the reminder information, the user of the terminal needs to confirm whether to update the major version number. The confirmation information can be "confirm to update the major version number".

[0072] Please see Figure 3In some embodiments, the update content of the major version number sent by the receiving terminal in step S110 may include, but is not limited to, steps S111 to S112:

[0073] Step S111: Receive update content of the main version number sent by the terminal, wherein the update content includes the version number of the main version number;

[0074] Step S112: Store the updated content to the log file and send the storage result to the terminal.

[0075] In step S111 of some embodiments, each update of the major version number will have a version number that needs to be changed and a program code that needs to be changed, with the version number and program code corresponding one-to-one.

[0076] In step S111 of some embodiments, the version number before modification and the version number after modification can be compared, and the corresponding content to be modified can be known according to the set modification rules. For example, if the version number before modification is 0.0.1.3, and the four digits represent the first component, the second component, the third component, and the fourth component respectively, and the version number after modification is 1.0.1.3, then it can be known that the content of the first component has been modified.

[0077] In step S112 of some embodiments, the updated content is stored in a log file, and the authentication end is granted permission to view it, so that the authentication end can view the updated content.

[0078] Please see Figure 4 In some embodiments, step S120 specifically includes steps S121 to S123:

[0079] Step S121: Obtain a preset list to find the authentication terminal in the list that corresponds to the main version number;

[0080] Step S122: Send the update notification of the major version number to the corresponding authentication terminal;

[0081] Step S123: Receive authentication information sent by the authentication terminal, wherein the authentication information is obtained by the authentication terminal executing a preset second script to obtain updated content and verify the updated content.

[0082] In step S121 of some embodiments, the manifest stores member information for all teams using the major version number, with each member corresponding to an authentication terminal, and the member information includes each member's email address.

[0083] In step S122 of some embodiments, the update notification may include a prior version number, and the authentication end knows the update content by reading the prior version number.

[0084] In step S123 of some embodiments, after the authentication terminal knows that the major version number has been updated, it can quickly find the log file corresponding to the updated content by executing a preset second script.

[0085] Please see Figure 5 In some embodiments, before step S130, that is, before receiving the selection information sent by the receiving terminal and confirming the updated major version number based on the selection information, the version number management method of this application embodiment may also include, but is not limited to, step S140:

[0086] Step S140: Execute a preset first script to obtain selection rules, wherein the selection rules represent the update method of the major version number.

[0087] In step S140 of some embodiments, updating the main version number by directly executing the first script in the background can effectively prevent the terminal from directly modifying the main version number.

[0088] In step S140 of some embodiments, after the first script is executed, multiple options will appear on the user interface of the terminal. The user of the terminal selects multiple options according to the update needs. This is a specific operation of the selection rules.

[0089] Figure 6 This is another optional flowchart of the version number management method provided in the embodiments of this application. Figure 6 The method may include, but is not limited to, steps S200 to S220.

[0090] Step S200: Display the option to update the major version number on the terminal according to the preset selection rules, and determine the selection information of the major version number according to the user's selection operation of the option to update the major version number. The selection information represents the version information of the major version number obtained by the terminal according to the preset selection rules.

[0091] Step S210: Send the main version number selection information to the system.

[0092] Step S220: Obtain the update content of the major version number and send the update content of the major version number to the system.

[0093] Steps S210 to S220 of this embodiment involve: First, displaying an option to update the major version number on the terminal according to preset selection rules, and determining the major version number selection information based on the user's selection of the option. The selection information represents the version information of the major version number obtained by the terminal according to the preset selection rules. Second, sending the major version number selection information to the system. Finally, obtaining the update content of the major version number and sending it to the system. In this method, when an update of the major version number is needed, the terminal sends the selection information to the system and confirms it. The terminal then sends the update content to the system. After completing the authentication process through the authentication terminal, the system updates the major version number. By streamlining the process on the system, unified updates of the major version number can be achieved. Furthermore, because of the added authentication process, users cannot arbitrarily change the major version number, thus preventing conflicts between major version numbers at the same time.

[0094] Please see Figure 7 In some embodiments, the version number management method may also include, but is not limited to, steps S230 to S240:

[0095] Step S230: Receive reminder information sent by the system based on the selected information;

[0096] Step S240: Send confirmation information to the system based on the reminder information, wherein the confirmation information indicates confirmation of updating the major version number.

[0097] In some embodiments, the version number management method applied to the system can also update the fix number. Since the fix number generally modifies existing problems, that is, the implementation of a specific function, the external interface and business logic will not change. Therefore, after the first script is executed, when the terminal displays multiple options containing the option to update the fix number, and the user of the terminal selects to update the fix number and sends it to the system, the system can directly update the fix number according to the user's selected update fix number, and then publish the update result.

[0098] In some embodiments, the version number management method applied to the system can also update the minor version number. Minor version numbers often arise when an interface becomes unusable, requiring modification or addition. Therefore, to clearly specify the modified or added content, it is required to input the content to update the minor version number, and the update description is saved in a log file. For example, the log file can be a changeList.log file. changeList.log can be understood as a file specifically for storing update content, and multiple changeList.log files can be created as needed, each corresponding to a major version number, minor version number, or fix number. The minor version number is only updated after the system confirms the update content of the minor version number input from the terminal.

[0099] The version number management method of the application embodiment will be further explained below in conjunction with the system end, terminal and authentication end.

[0100] In some embodiments, when the first script is executed, the first script is usually stored in the terminal. Users need to execute the first script to update the major version number, minor version number, or patch number. In other words, the entry point for updating the major version number, minor version number, or patch number can only be obtained by executing the first script. Therefore, this method can effectively prevent the operation of directly updating the version number.

[0101] In some embodiments, after executing the first script, an input interface is displayed on the terminal, enabling interaction with the system. Specifically, the terminal input interface displays three options: major version number, minor version number, and patch number, prompting the user to select one of these options. Furthermore, it can be configured to allow multiple selections simultaneously. For example, if the user chooses to modify both the major version number and the patch number, by configuring the input interface and the system's response, both the major version number and the patch number can be updated concurrently, improving the efficiency of version number updates.

[0102] In some embodiments, when a user selects a repair number on the terminal, it can be modified directly through the system. Since a repair number typically modifies an existing problem—that is, a specific implementation—the external interface and business logic remain unchanged. Therefore, there are two ways to update the repair number: one is that the terminal can directly update the repair number after executing the first script, and then the terminal publishes the updated repair number; the other is that the terminal sends a request to update the repair number to the system, and the system updates the repair number directly upon receiving the request.

[0103] In some embodiments, when a user selects to update the minor or major version number, they must also enter and confirm the update content before the minor or major version number is updated based on the input. For minor version numbers, this often indicates an unusable interface that needs modification or addition. For major version numbers, this occurs when business function components are not backward compatible, requiring incremental changes.

[0104] In some embodiments, for minor or major version numbers that need to be updated, the version number and program code included in the update content must be entered through the terminal and sent to the system for storage. The system will save the update description in the changeList.log file and return the storage result to the user on the terminal.

[0105] In some embodiments, the minor version number or major version number is updated only after the terminal confirms the update content.

[0106] In some embodiments, for an updated major version number, the system will send a reminder message to the terminal, which will then remind the user whether to confirm the update of the major version number. After the user confirms the update of the major version number, the terminal will ask the user to enter the update content and save the update content.

[0107] In some embodiments, after the terminal confirms the update content, the system does not directly update the major version number. Instead, the system creates a preliminary version number, which is used as a temporary version number to identify the update content.

[0108] In some embodiments, after creating a preliminary version number, the system automatically sends a notification email to each member's authentication terminal based on the team member list, informing them of the major version number update. Upon receiving the email, members on the authentication terminals execute a second script to view the log file, obtain the update content, and sign it with their employee ID. Specifically, the second script can reside on the terminal corresponding to the authentication terminal; for example, the second script can be stored on the authentication terminal's computer. By executing the second script, the log file can be accessed to obtain the update content. Once all team members have completed the confirmation, the preliminary version number is converted to the changed major version number.

[0109] In some embodiments, the use of a preliminary version number can clearly indicate that the modification of the major version number has not yet been confirmed and requires authentication. For example, the format of the preliminary version number can be set as: XYZ[ac][positive integer], where X, Y, and Z are the major version number, minor version number, and fix number, respectively, and XYZ is the overall version number. Assuming the version number before modification is 1.0.0 and the version number after modification is 2.0.0, the preliminary version number is 2.0.0.a1, 2.0.0.b99, or 2.0.0.c1000. Through the preliminary version number, it can be clearly known that the update content and the modification of the major version number corresponding to the preliminary version number have not yet been confirmed.

[0110] Please see Figure 8 This application also provides a version number management device that can implement the above-described version number management method. The device includes:

[0111] The option operation module 200 is used to display the option to update the main version number on the terminal according to the preset selection rules, and to determine the selection information of the main version number according to the user's selection operation of the option to update the main version number. The selection information represents the version information of the main version number obtained by the terminal according to the preset selection rules.

[0112] Select the sending module 210, which is used to send the selection information of the main version number to the system.

[0113] The content sending module 220 is used to obtain the update content of the major version number and send the update content of the major version number to the system.

[0114] The update module 230 is used to receive selection information sent by the terminal and confirm the major version number to be updated based on the selection information.

[0115] Module 240 is used to receive the update content of the major version number sent by the terminal and create a preliminary version number, wherein the preliminary version number represents the update content of the major version number.

[0116] The notification authentication module 250 is used to send the update notification of the main version number to the authentication end, so that the authentication end can execute the authentication process and obtain authentication information confirming the updated content.

[0117] The version update module 260 is used to receive authentication information sent by the authentication terminal confirming the update content, and change the previous version number to the updated major version number according to the authentication information and the update content.

[0118] In some embodiments, selecting update module 230 may include:

[0119] The reminder sending unit sends reminder information to the terminal based on the selected information.

[0120] The receiving confirmation unit receives confirmation information sent by the terminal based on the reminder information, wherein the confirmation information indicates confirmation of updating the major version number.

[0121] In some embodiments, the creation module 240 may include:

[0122] The update receiving unit receives update content of the major version number sent by the terminal, wherein the update content includes the version number of the major version number;

[0123] The storage log unit stores the updated content to the log file and sends the storage results to the terminal.

[0124] In some embodiments, the notification authentication module 250 may include:

[0125] The list acquisition unit retrieves a preset list to find the authentication endpoint corresponding to the main version number in the list;

[0126] Update the sending unit to send the update notification of the major version number to the corresponding authentication terminal;

[0127] The authentication receiving unit receives authentication information sent by the authentication terminal. The authentication information is obtained by the authentication terminal executing a preset second script to obtain updated content and verify the updated content.

[0128] This application also provides an electronic device, which includes: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for communication between the processor and the memory. When the program is executed by the processor, it implements the version number management method described above. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0129] Please see Figure 9 , Figure 9 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:

[0130] The processor 300 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0131] The memory 310 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 310 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 310 and is called and executed by the processor 300 using the version number management method of the embodiments of this application.

[0132] The input / output interface 320 is used to implement information input and output;

[0133] The communication interface 330 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0134] Bus 340 transmits information between various components of the device (e.g., processor 300, memory 310, input / output interface 320, and communication interface 330);

[0135] The processor 300, memory 310, input / output interface 320 and communication interface 330 are connected to each other within the device via bus 340.

[0136] This application also provides a storage medium, which is a computer-readable storage medium for computer-readable storage. The storage medium stores one or more programs, which can be executed by one or more processors to implement the above-described version number management method.

[0137] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0138] The version number management method, apparatus, electronic device, and storage medium of this application embodiment firstly receive selection information sent by a terminal and confirm the updated major version number according to the selection information, wherein the selection information represents the version information of the major version number obtained by the terminal according to a preset selection rule; secondly, the system receives the update content of the major version number sent by the terminal and creates a preliminary version number, wherein the preliminary version number represents the update content of the major version number; then, the update notification of the major version number is sent to the authentication end so that the authentication end executes the authentication process and obtains authentication information confirming the update content; finally, the system receives the authentication information confirming the update content sent by the authentication end and changes the preliminary version number to the updated major version number according to the authentication information and the update content. In this method, when the major version number needs to be updated, the terminal sends the selection information for updating the major version number to the system and confirms it. The terminal then sends the updated major version number to the system. After the system completes the authentication process through the authentication terminal, it updates the major version number. By streamlining the process on the system side, the major version number can be updated uniformly. Furthermore, because of the added authentication process, the major version number will not be changed arbitrarily, thus avoiding the problem of conflicting major version numbers at the same time.

[0139] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0140] It will be understood by those skilled in the art that Figure 1-7 The technical solutions shown do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0141] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0142] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0143] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0144] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0145] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0146] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0147] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0148] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0149] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A version number management method characterized by comprising: Applied to a system end, the method comprises: Receiving selection information sent by a terminal, and confirming an updated main version number according to the selection information, wherein the selection information represents version information of the main version number obtained by the terminal according to a preset selection rule; Receiving update content of the main version number sent by the terminal, and creating a preceding version number, wherein the preceding version number represents the update content of the main version number, and the update content comprises a version number of the main version number; Storing the update content to a log file, and sending a storage result to the terminal; Obtaining a preset list to find an authentication end corresponding to the main version number in the list; Sending update notification of the main version number to the corresponding authentication end; Receiving authentication information sent by the authentication end, wherein the authentication information is obtained by the authentication end by executing a preset second script to verify the update content; Receiving the authentication information sent by the authentication end to confirm the update content, and changing the preceding version number to an updated main version number according to the authentication information and the update content.

2. The version number management method of claim 1, wherein, The confirming of the updated main version number according to the selection information comprises: Sending reminding information to the terminal according to the selection information; Receiving confirmation information sent by the terminal according to the reminding information, wherein the confirmation information represents confirmation of updating the main version number.

3. The version number management method of claim 1, wherein, Before the receiving of the selection information sent by the terminal and the confirming of the updated main version number according to the selection information, the method further comprises: Executing a preset first script to obtain the selection rule, wherein the selection rule represents an update mode of the main version number.

4. A version number management method characterized by, Applied to a terminal, the method comprises: Displaying an option of updating a main version number on the terminal according to a preset selection rule, and determining selection information of the main version number according to a selection operation of a user on the option of updating the main version number, wherein the selection information represents version information of the main version number obtained by the terminal according to a preset selection rule; Sending the selection information of the main version number to a system end; Obtaining update content of the main version number, and sending the update content of the main version number to the system end.

5. The version number management method of claim 4, wherein, The method further comprises: Receiving reminding information sent by the system end according to the selection information; Sending confirmation information to the system end according to the reminding information, wherein the confirmation information represents confirmation of updating the main version number.

6. A version number management apparatus characterized by comprising: Comprise: An option operation module, configured to display an option of updating a main version number on a terminal according to a preset selection rule, and determine selection information of the main version number according to a selection operation of a user on the option of updating the main version number, wherein the selection information represents version information of the main version number obtained by the terminal according to a preset selection rule; A selection sending module, configured to send the selection information of the main version number to a system end; A content sending module, configured to obtain update content of the main version number, and send the update content of the main version number to the system end; The selection updating module is configured to receive the selection information sent by the terminal and confirm the updated master version number according to the selection information. The creation module is configured to receive the update content of the master version number sent by the terminal and create a preceding version number, store the update content to a log file, and send the storage result to the terminal. The preceding version number represents the update content of the master version number, and the update content includes a version number of the master version number. The notification authentication module is configured to obtain a preset list to find an authentication terminal corresponding to the master version number in the list, send an update notification of the master version number to the corresponding authentication terminal, and receive authentication information sent by the authentication terminal. The authentication information is obtained by the authentication terminal by executing a preset second script to obtain the update content and verify the update content. The version updating module is configured to receive the authentication information sent by the authentication terminal to confirm the update content, and change the preceding version number to an updated master version number according to the authentication information and the update content.

7. An electronic device, comprising: The electronic device includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for realizing connection communication between the processor and the memory. The program is executed by the processor to realize the steps of the version number management method according to any one of claims 1 to 5.

8. A storage medium, the storage medium being a computer-readable storage medium for computer-readable storage, characterized in that, The storage medium stores one or more programs executable by one or more processors to realize the steps of the version number management method according to any one of claims 1 to 5.

Images